mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 20. Authenticating third-party clients through RH-SSO To use the different remote services provided by Business Central or by KIE Server, your client, such as curl, wget, web browser, or a custom REST client, must authenticate through the RH-SSO server and have a valid token to perform the requests. To use the remote services, the authenticated user must have the following roles: rest-all for using Business Central remote services. kie-server for using the KIE Server remote services. Use the RH-SSO Admin Console to create these roles and assign them to the users that will consume the remote services. Your client can authenticate through RH-SSO using one of these options: Basic authentication, if it is supported by the client Token-based authentication 20.1. Basic authentication If you enabled basic authentication in the RH-SSO client adapter configuration for both Business Central and KIE Server, you can avoid the token grant and refresh calls and call the services as shown in the following examples: For web based remote repositories endpoint: For KIE Server: 20.2. Token-based authentication If you want a more secure option of authentication, you can consume the remote services from both Business Central and KIE Server by using a granted token provided by RH-SSO. Procedure In the RH-SSO Admin Console, click the Clients menu item and click Create to create a new client. The Add Client page opens. On the Add Client page, provide the required information to create a new client for your realm. For example: Client ID : kie-remote Client protocol : openid-connect Click Save to save your changes. Change the token settings in Realm Settings : In the RH-SSO Admin Console, click the Realm Settings menu item. Click the Tokens tab. Change the value for Access Token Lifespan to 15 minutes. This gives you enough time to get a token and invoke the service before it expires. Click Save to save your changes. After a public client for your remote clients is created, you can now obtain the token by making an HTTP request to the RH-SSO server's token endpoint using: The user in this command is a Business Central RH-SSO user. For more information, see Section 17.1, "Adding Red Hat Decision Manager users" . To view the token obtained from the RH-SSO server, use the following command: You can now use this token to authorize the remote calls. For example, if you want to check the internal Red Hat Decision Manager repositories, use the token as shown below:

Commands:
curl http://admin:password@localhost:8080/business-central/rest/repositories
curl http://admin:password@localhost:8080/kie-server/services/rest/server/
RESULT=`curl --data "grant_type=password&client_id=kie-remote&username=admin&password=password" http://localhost:8180/auth/realms/demo/protocol/openid-connect/token`
TOKEN=`echo USDRESULT | sed 's/.*access_token":"//g' | sed 's/".*//g'`
curl -H "Authorization: bearer USDTOKEN" http://localhost:8080/business-central/rest/repositories
Chapter 3. Data Grid on OpenShift 3.1. Data Grid 8.4 images Data Grid 8.4 includes two container images, the Data Grid Operator image and Data Grid Server image. Data Grid images are hosted on the Red Hat Container Registry, where you can find health indexes for the images along with information about each tagged version. Custom Data Grid Deployments Red Hat does not support customization of any 8.4 images from the Red Hat Container Registry through the Source-to-Image (S2I) process or ConfigMap API. As a result it is not possible to use custom: Discovery protocols JGroups SYM_ENCRYPT or ASYM_ENCRYPT encryption mechanisms Additional resources Data Grid Container Images 3.2. Embedded caches on OpenShift Using embedded Data Grid caches in applications running on OpenShift, which was referred to as Library Mode in releases, is intended for specific uses only: Using local or distributed caching in custom Java applications to retain full control of the cache lifecycle. Additionally, when using features that are available only with embedded Data Grid such as distributed streams. Reducing network latency to improve the speed of cache operations. The Hot Rod protocol provides near-cache capabilities that achieve equivalent performance to a standard client-server architecture. Requirements Embedding Data Grid in applications running on OpenShift requires you to use a discovery mechanism so Data Grid nodes can form clusters to replicate and distribute data. Red Hat supports only DNS_PING as the cluster discovery mechanism. DNS_PING exposes a port named ping that Data Grid nodes use to perform discovery and join clusters. TCP is the only supported protocol for the ping port, as in the following example for a pod on OpenShift: spec: ... ports: - name: ping port: 8888 protocol: TCP targetPort: 8888 Limitations Embedding Data Grid in applications running on OpenShift also has some specific limitations: Persistent cache stores are not currently supported. UDP is not supported with embedded Data Grid. Custom caching services Red Hat highly discourages embedding Data Grid to build custom caching servers to handle remote client requests. To benefit from regular, automatic updates with performance improvements and fix security issues, you should create Data Grid clusters with the Data Grid Operator instead. Additional resources Embedding Data Grid in Java Applications

Commands:
spec: ports: - name: ping port: 8888 protocol: TCP targetPort: 8888
Chapter 1. Migrating Red Hat Single Sign-On 7.6 to Red Hat build of Keycloak The purpose of this guide is to document the steps that are required to successfully migrate Red Hat Single Sign-On 7.6 to Red Hat build of Keycloak 22.0. The instructions address migration of the following elements: Red Hat Single Sign-On 7.6 server Operator deployments on OpenShift Template deployments on OpenShift Applications secured by Red Hat Single Sign-On 7.6 Custom providers Custom themes This guide also includes guidelines for migrating upstream Keycloak to Red Hat build of Keycloak 22.0. Before you start the migration, you might consider installing a new instance of Red Hat build of Keycloak to become familiar with the changes for this release. See the Red Hat build of Keycloak Getting Started Guide .

Commands:
17.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: named_write_master_zones When disabled, this Boolean prevents named from writing to zone files or directories labeled with the named_zone_t type. The daemon does not usually need to write to zone files; but in the case that it needs to, or if a secondary server needs to write to zone files, enable this Boolean to allow this action. named_tcp_bind_http_port When enabled, this Boolean allows BIND to bind an Apache port. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, enter the following command: Enter the following command to view description of a particular Boolean: Note that the additional policycoreutils-devel package providing the sepolicy utility is required for this command to work.

Commands:
~]USD getsebool -a | grep service_name
~]USD sepolicy booleans -b boolean_name
5.263. python 5.263.1. RHBA-2012:1250 - python bug fix update Updated python packages that fix a bug are now available for Red Hat Enterprise Linux 6. Python is an interpreted, interactive, object-oriented programming language. Python includes modules, classes, exceptions, high-level dynamic data types, and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems (X11, Motif, Tk, Mac and MFC). Bug Fix BZ# 848815 As part of the fix for CVE-2012-0876, a new symbol ("XML_SetHashSalt") was added to the system libexpat library, and which Python's standard library uses within the pyexpat module. If an unpatched libexpat.so.1 was present in a directory listed in LD_LIBRARY_PATH, then attempts to use the pyexpat module (such as within yum) would fail with an ImportError exception. This update adds an RPATH directive to pyexpat to ensure that the system libexpat is used by pyexpat, regardless of whether there is an unpatched libexpat within the LD_LIBRARY_PATH, thus preventing the ImportError exception. All Python users are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 9. Sources The updated Red Hat Ceph Storage source code packages are available at the following location: For Red Hat Enterprise Linux 8: http://ftp.redhat.com/redhat/linux/enterprise/8Base/en/RHCEPH/SRPMS/ For Red Hat Enterprise Linux 9: http://ftp.redhat.com/redhat/linux/enterprise/9Base/en/RHCEPH/SRPMS/

Commands:
Appendix A. The Device Mapper The Device Mapper is a kernel driver that provides a generic framework for volume management. It provides a generic way of creating mapped devices, which may be used as logical volumes. It does not specifically know about volume groups or metadata formats. The Device Mapper provides the foundation for a number of higher-level technologies. In addition to LVM, device-mapper multipath and the dmraid command use the Device Mapper. The user interface to the Device Mapper is the ioctl system call. LVM logical volumes are activated using the Device Mapper. Each logical volume is translated into a mapped device, Each segment translates into a line in the mapping table that describes the device. The Device Mapper provides linear mapping, striped mapping, and error mapping, amongst others. Two disks can be concatenated into one logical volume with a pair of linear mappings, one for each disk. The dmsetup command is a command line wrapper for communication with the Device Mapper. It provides complete access to the ioctl commands through the libdevmapper command. For general system information about LVM devices, you may find the dmsetup info command to be useful. For information about the options and capabilities of the dmsetup command, see the dmsetup (8) man page.

Commands:
12.11. Turning Schema Checking On and Off When schema checking is on, the Directory Server ensures three things: The object classes and attributes using are defined in the directory schema. The attributes required for an object class are contained in the entry. Only attributes allowed by the object class are contained in the entry. Important Red Hat recommends not to disable the schema checking. Schema checking is turned on by default in the Directory Server, and the Directory Server should always run with schema checking turned on. The only situation where is may be beneficial to turn schema checking off is to accelerate LDAP import operations. However, there is a risk of importing entries that do not conform to the schema. Consequently, it is impossible to update these entries. 12.11.1. Turning Schema Checking On and Off Using the Command Line To turn schema checking on and off, set the value of the nsslapd-schemacheck parameter. For example to disable schema checking: For details about the nsslapd-schemacheck parameter, see the description of the parameter in the Red Hat Directory Server Configuration, Command, and File Reference . 12.11.2. Turning Schema Checking On and Off Using the Web Console To enable or disable schema checking using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Open the Server Settings , and select the Server Settings entry. Open the Advanced Settings tab. To enable schema checking, select the Enable Schema Checking check box. To disable the feature, clear the check box. Click Save .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-schemacheck=off Successfully replaced "nsslapd-schemacheck"
Chapter 28. Network Driver Updates The bna driver has been upgraded to version 3.2.23.0r. The cxgb3 driver has been upgraded to version 1.1.5-ko. The cxgb3i driver has been upgraded to version 2.0.0. The iw_cxgb3 driver has been upgraded to version 1.1. The cxgb4 driver has been upgraded to version 2.0.0-ko. The cxgb4vf driver has been upgraded to version 2.0.0-ko. The cxgb4i driver has been upgraded to version 0.9.4. The iw_cxgb4 driver has been upgraded to version 0.1. The e1000e driver has been upgraded to version 2.3.2-k. The igb driver has been upgraded to version 5.2.13-k. The igbvf driver has been upgraded to version 2.0.2-k. The ixgbe driver has been upgraded to version 3.19.1-k. The ixgbevf driver has been upgraded to version 2.12.1-k. The i40e driver has been upgraded to version 1.0.11-k. The i40evf driver has been upgraded to version 1.0.1. The e1000 driver has been upgraded to version 7.3.21-k8-NAPI. The mlx4_en driver has been upgraded to version 2.2-1. The mlx4_ib driver has been upgraded to version 2.2-1. The mlx5_core driver has been upgraded to version 2.2-1. The mlx5_ib driver has been upgraded to version 2.2-1. The ocrdma driver has been upgraded to version 10.2.287.0u. The ib_ipoib driver has been upgraded to version 1.0.0. The ib_qib driver has been upgraded to version 1.11. The enic driver has been upgraded to version 2.1.1.67. The be2net driver has been upgraded to version 10.4r. The tg3 driver has been upgraded to version 3.137. The r8169 driver has been upgraded to version 2.3LK-NAPI.

Commands:
Chapter 6. Networking dashboards Networking metrics are viewable in dashboards within the OpenShift Container Platform web console, under Observe Dashboards . 6.1. Network Observability Operator If you have the Network Observability Operator installed, you can view network traffic metrics dashboards by selecting the Netobserv dashboard from the Dashboards drop-down list. For more information about metrics available in this Dashboard , see Network Observability metrics dashboards . 6.2. Networking and OVN-Kubernetes dashboard You can view both general networking metrics as well as OVN-Kubernetes metrics from the dashboard. To view general networking metrics, select Networking/Linux Subsystem Stats from the Dashboards drop-down list. You can view the following networking metrics from the dashboard: Network Utilisation , Network Saturation , and Network Errors . To view OVN-Kubernetes metrics select Networking/Infrastructure from the Dashboards drop-down list. You can view the following OVN-Kuberenetes metrics: Networking Configuration , TCP Latency Probes , Control Plane Resources , and Worker Resources . 6.3. Ingress Operator dashboard You can view networking metrics handled by the Ingress Operator from the dashboard. This includes metrics like the following: Incoming and outgoing bandwidth HTTP error rates HTTP server response latency To view these Ingress metrics, select Networking/Ingress from the Dashboards drop-down list. You can view Ingress metrics for the following categories: Top 10 Per Route , Top 10 Per Namespace , and Top 10 Per Shard .

Commands:
D.9. Description View The Description View provides a means to display and edit (add, change or remove) a description for any model or model object. To show the Description View , click Window > Show View > Other... to display the Eclipse Show View dialog. Click Teiid Designer > Description view and then click OK . Figure D.18. Description View You can click the edit description action in the toolbar or right-click select Edit in the context menu to bring up the Edit Description dialog. Figure D.19. Description View Context Menu Figure D.20. Edit Description Dialog

Commands:
Chapter 29. Upgrading Your Current System The procedure for performing an in-place upgrade on your current system is handled by the following utilities: The Preupgrade Assistant , which is a diagnostics utility that assesses your current system and identifies potential problems you might encounter during or after the upgrade. The Red Hat Upgrade Tool utility, which is used to upgrade a system from Red Hat Enterprise Linux version 6 to version 7. Note In-place upgrades are currently only supported on AMD64 and Intel 64 ( x86_64 ) systems and on IBM Z ( s390x ). Additionally, only the Server variant can be upgraded with Red Hat Upgrade Tool . Full documentation covering the process of upgrading from an earlier release of Red Hat Enterprise Linux to Red Hat Enterprise Linux 7 is available in the Red Hat Enterprise Linux 7 Migration Planning Guide . You can also use the Red Hat Enterprise Linux Upgrade Helper to guide you through migration from Red Hat Enterprise Linux 6 to 7.

Commands:
7.23. cifs-utils 7.23.1. RHBA-2013:0408 - cifs-utils bug fix and enhancement update Updated cifs-utils packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The SMB/CIFS protocol is a standard file sharing protocol widely deployed on Microsoft Windows machines. This package contains tools for mounting shares on Linux using the SMB/CIFS protocol. The tools in this package work in conjunction with support in the kernel to allow one to mount a SMB/CIFS share onto a client and use it as if it were a standard Linux file system. Bug Fixes BZ#856729 When the mount.cifs utility ran out of addresses to try, it returned the "System error" error code (EX_SYSERR) to the caller service. The utility has been modified and it now correctly returns the "Mount failure" error code (EX_FAIL). BZ#826825 Typically, "/" characters are not allowed in user names for Microsoft Windows systems, but they are common in certain types of kerberos principal names. However, mount.cifs previously allowed the use of "/" in user names, which caused attempts to mount CIFS file systems to fail. With this package, "/" characters are now allowed in user names if the "sec=krb5" or "sec=krb5i" mount options are specified, thus CIFS file systems can now be mounted as expected. BZ# 838606 Previously, the cifs-utils packages were compiled without the RELRO (read-only relocations) and PIE (Position Independent Executables) flags. Programs provided by this package could be vulnerable to various attacks based on overwriting the ELF section of a program. The "-pie" and "-fpie" options enable the building of position-independent executables, and the "-Wl","-z","relro" turns on read-only relocation support in gcc. These options are important for security purposes to guard against possible buffer overflows that lead to exploits. The cifs-utils binaries are now built with PIE and full RELRO support. The cifs-utils binary is now more secured against "return-to-text" and memory corruption attacks and also against attacks based on the program's ELF section overwriting. Enhancements BZ#843596 With this update, the "strictcache", "actimeo", "cache=" and "rwpidforward" mount options are now documented in the mount.cifs(8) manual page. BZ#843612 The "getcifsacl", "setcifsacl" and "cifs.idmap" programs have been added to the package. These utilities allow users to manipulate ACLs on CIFS shares and allow the mapping of Windows security IDs to POSIX user and group IDs. BZ#843617 With this update, the cifs.idmap helper, which allows SID to UID and SID to GID mapping, has been added to the package. Also, the manual page cifs.upcall(8) has been updated and cifs.idmap(8) has been added. Users of cifs-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
3.4. Renewing certificates before they expire In Red Hat Virtualization earlier than version 4.4 SP1, all certificates followed a 398 day lifetime. Starting in Red Hat Virtualization version 4.4 SP1, the self-signed internal certificates between hypervisors and the Manager follow a five year lifetime. Certificates visible to web browsers still follow the standard 398 day lifetime and must be renewed once per year. Warning Do not let certificates expire. If they expire, the host and Manager stop responding, and recovery is an error-prone and time-consuming process. Procedure Renew the host certificates: In the Administration Portal, click Compute Hosts . Click Management Maintenance and then click OK . The virtual machines should automatically migrate away from the host. If they are pinned or otherwise cannot be migrated, you must shut them down. When the host is in maintenance mode and there are no more virtual machines remaining on this host, click Installation Enroll Certificate . When enrollment is complete, click Management Activate . Renew the Manager certificates: Self-hosted engine only: log in to the host and put it in global maintenance mode. Self-hosted engine and standalone Manager: log in to the Manager and run engine-setup . The engine-setup script prompts you with configuration questions. Respond to the questions as appropriate or use an answers file. Enter Yes after the following engine-setup prompt: Self-hosted engine only: log in to the host and disable global maintenance mode: Additional resources How to manually renew RHV host SSL certificate if expired?

Commands:
hosted-engine --set-maintenance --mode=global
engine-setup --offline
Renew certificates? (Yes, No) [Yes]:
hosted-engine --set-maintenance --mode=none
Chapter 1. Introduction to developing applications with Red Hat build of Apache Camel for Quarkus This guide is for developers writing Camel applications on top of Red Hat build of Apache Camel for Quarkus. Camel components which are supported in Red Hat build of Apache Camel for Quarkus have an associated Red Hat build of Apache Camel for Quarkus extension. For more information about the Red Hat build of Apache Camel for Quarkus extensions supported in this distribution, see the Red Hat build of Apache Camel for Quarkus Reference reference guide.

Commands: