mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 10. Configuring reCAPTCHA for 3scale API Management This document describes how to configure reCAPTCHA for Red Hat 3scale API Management On-premises to protect against spam. Prerequisites An installed and configured 3scale On-premises instance on a supported OpenShift version . Get a site key and the secret key for reCAPTCHA v2. See the Register a new site web page. Add the Developer Portal domain to an allowlist if you want to use domain name validation. To configure reCAPTCHA for 3scale, perform the steps outlined in the following procedure: Section 10.1, "Configuring reCAPTCHA for spam protection in 3scale API Management" 10.1. Configuring reCAPTCHA for spam protection in 3scale API Management To configure reCAPTCHA for spam protection, you have two options to patch the secret file that contains the reCAPTCHA. These options are in the OpenShift Container Platform (OCP) user interface or using the command line interface (CLI). Procedure OCP 4.x: Navigate to Project: [Your_project_name] > Workloads > Secrets . Edit the system-recaptcha secret file. The PRIVATE_KEY and PUBLIC_KEY from the reCAPTHCA service must be in base64 format encoding. Transform the keys to base64 encoding manually. Note The CLI reCAPTCHA option does not require base64 format encoding. CLI: Type the following command: USD oc patch secret/system-recaptcha -p '{"stringData": {"PUBLIC_KEY": "public-key-from-service", "PRIVATE_KEY": "private-key-from-service"}}' Post-procedure steps Redeploy the system pod after you have completed one of the above options. In the 3scale Admin Portal, turn on spam protection against users that are not signed: Navigate to Audience > Developer Portal > Spam Protection . Select one of the following options: Always reCAPTCHA will always appear when a form is presented to a user who is not logged in. Suspicious only reCAPTCHA is only shown if the automated checks detect a possible spammer. Never Turns off Spam protection. After system-app has redeployed, the pages that use spam protection on the Developer Portal will show the reCAPTCHA I'm not a robot checkbox. Additional resources See ReCAPTCHA home page for more information, guides, and support.

Commands:
oc patch secret/system-recaptcha -p '{"stringData": {"PUBLIC_KEY": "public-key-from-service", "PRIVATE_KEY": "private-key-from-service"}}'
Chapter 10. Variables of the postfix role in System Roles The postfix role variables allow the user to install, configure, and start the postfix Mail Transfer Agent (MTA). The following role variables are defined in this section: postfix_conf : It includes key/value pairs of all the supported postfix configuration parameters. By default, the postfix_conf does not have a value. If your scenario requires removing any existing configuration and apply the desired configuration on top of a clean postfix installation, specify the : replaced option within the postfix_conf dictionary: An example with the : replaced option: postfix_check : It determines if a check has been executed before starting the postfix to verify the configuration changes. The default value is true. For example: postfix_backup : It determines whether a single backup copy of the configuration is created. By default the postfix_backup value is false. To overwrite any backup run the following command: If the postfix_backup value is changed to true , you must also set the postfix_backup_multiple value to false. For example: postfix_backup_multiple : It determines if the role will make a timestamped backup copy of the configuration. To keep multiple backup copies, run the following command: By default the value of postfix_backup_multiple is true. The postfix_backup_multiple:true setting overrides postfix_backup . If you want to use postfix_backup you must set the postfix_backup_multiple:false . postfix_manage_firewall : Integrates the postfix role with the firewall role to manage port access. By default, the variable is set to false . If you want to automatically manage port access from the postfix role, set the variable to true . postfix_manage_selinux : Integrates the postfix role with the selinux role to manage port access. By default, the variable is set to false . If you want to automatically manage port access from the postfix role, set the variable to true . Important The configuration parameters cannot be removed. Before running the postfix role, set the postfix_conf to all the required configuration parameters and use the file module to remove /etc/postfix/main.cf . 10.1. Additional resources /usr/share/doc/rhel-system-roles/postfix/README.md

Commands:
postfix_conf: relayhost: example.com
postfix_conf: relayhost: example.com previous: replaced
postfix_check: true
*cp /etc/postfix/main.cf /etc/postfix/main.cf.backup*
postfix_backup: true postfix_backup_multiple: false
*cp /etc/postfix/main.cf /etc/postfix/main.cf.USD(date -Isec)*
11.3. Installation Tools IBM Installation Toolkit is an optional tool that speeds up the installation of Linux and is especially helpful for those unfamiliar with Linux. Use the IBM Installation Toolkit for the following actions: [5] Install and configure Linux on a non-virtualized Power Systems server. Install and configure Linux on servers with previously-configured logical partitions (LPARs, also known as virtualized servers). Install IBM service and productivity tools on a new or previously installed Linux system. The IBM service and productivity tools include dynamic logical partition (DLPAR) utilities. Upgrade system firmware level on Power Systems servers. Perform diagnostics or maintenance operations on previously installed systems. Migrate a LAMP server (software stack) and application data from a System x to a System p system. A LAMP server is a bundle of open source software. LAMP is an acronym for Linux, Apache HTTP Server , MySQL relational database, and PHP (Perl or Python) scripting language. Documentation for the IBM Installation Toolkit for PowerLinux is available in the Linux Information Center at http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaan%2Fpowerpack.htm PowerLinux service and productivity tools is an optional set of tools that include hardware service diagnostic aids, productivity tools, and installation aids for Linux operating systems on IBM servers based on POWER7, POWER6, POWER5, and POWER4 technology. Documentation for the service and productivity tools is available in the Linux Information Center at http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaau%2Fliaauraskickoff.htm [5] Parts of this section were previously published at IBM's Linux information for IBM systems resource at http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaay%2Ftools_overview.htm

Commands:
Chapter 11. Red Hat Fuse and Red Hat Decision Manager Red Hat Fuse is a distributed, cloud-native integration platform that is part of an agile integration solution. Its distributed approach enables teams to deploy integrated services where required. Fuse has the flexibility to service diverse users, including integration experts, application developers, and business users, each with their own choice of deployment, architecture, and tooling. The API-centric, container-based architecture decouples services so they can be created, extended, and deployed independently. The result is an integration solution that supports collaboration across the enterprise. Red Hat Decision Manager is an open source decision management platform that combines business rules management, complex event processing, Decision Model & Notation (DMN) execution, and Red Hat build of OptaPlanner for solving planning problems. It automates business decisions and makes that logic available to the entire business. Business assets such as rules, decision tables, and DMN models are organized in projects and stored in the Business Central repository. This ensures consistency, transparency, and the ability to audit across the business. Business users can modify business logic without requiring assistance from IT personnel. You can install Red Hat Fuse on the Apache Karaf container platform and then install and configure Red Hat Process Automation Manager in that container. You can also install Red Hat Fuse on a separate instance of Red Hat JBoss Enterprise Application Platform and integrate it with Red Hat Process Automation Manager. The kie-camel module provides integration between Red Hat Fuse and Red Hat Process Automation Manager. Important For the version of Red Hat Fuse that Red Hat Decision Manager 7.13 supports, see Red Hat Decision Manager 7 Supported Configurations . Note You can install Red Hat Fuse on Spring Boot. Red Hat Decision Manager provides no special integration for this scenario. You can use the kie-server-client library in an application running on Red Hat Fuse on Spring Boot to enable communication with Red Hat Decision Manager services running on a KIE Server. For instructions about using the kie-server-client library, see Interacting with Red Hat Decision Manager using KIE APIs .

Commands:
Chapter 57. Networking Verification of signatures using the MD5 hash algorithm is disabled in Red Hat Enterprise Linux 7 It is impossible to connect to any Wi-Fi Protected Access (WPA) Enterprise Access Point (AP) that requires MD5 signed certificates. To work around this problem, copy the wpa_supplicant.service file from the /usr/lib/systemd/system/ directory to the /etc/systemd/system/ directory and add the following line to the Service section of the file: Then run the systemctl daemon-reload command as root to reload the service file. Important: Note that MD5 certificates are highly insecure and Red Hat does not recommend using them. (BZ#1062656) Mellanox PMD in DPDK causes a performance drop when IOMMU is enabled inside the guest When running Mellanox Poll Mode Driver (PMD) in Data Plane Development Kit (DPDK) in the guest, a performance drop is expected if the iommu=pt option is not set. To make Mellanox PMD work properly, I/O memory management unit (IOMMU) needs to be explicitly enabled in the kernel, and use the passthrough mode. For doing that, pass the intel_iommu=on option (for Intel systems) to the kernel command line. In addition, use iommu=pt to have a proper I/O performance. (BZ#1578688) freeradius might fail when upgrading from RHEL 7.3 A new configuration property, correct_escapes , in the /etc/raddb/radiusd.conf file was introduced in the freeradius version distributed since RHEL 7.4. When an administrator sets correct_escapes to true , the new regular expression syntax for backslash escaping is expected. If correct_escapes is set to false , the old syntax is expected where backslashes are also escaped. For backward compatibility reasons, false is the default value. When upgrading, configuration files in the /etc/raddb/ directory are overwritten unless modified by the administrator, so the value of correct_escapes might not always correspond to which type of syntax is used in all the configuration files. As a consequence, authentication with freeradius might fail. To prevent the problem from occurring, after upgrading from freeradius version 3.0.4 (distributed with RHEL 7.3) and earlier, make sure all configuration files in the /etc/raddb/ directory use the new escaping syntax (no double backslash characters can be found) and that the value of correct_escapes in /etc/raddb/radiusd.conf is set to true . For more information and examples, see the solution at https://access.redhat.com/solutions/3241961 . (BZ#1489758)

Commands:
Environment=OPENSSL_ENABLE_MD5_VERIFY=1
Chapter 2. Installing the MTA extension for Visual Studio Code You can install the MTA extension for Visual Studio Code (VS Code). Prerequisites The following are the prerequisites for the Migration Toolkit for Applications (MTA) installation: Java Development Kit (JDK) is installed. MTA supports the following JDKs: OpenJDK 11 OpenJDK 17 Oracle JDK 11 Oracle JDK 17 Eclipse TemurinTM JDK 11 Eclipse TemurinTM JDK 17 8 GB RAM macOS installation: the value of maxproc must be 2048 or greater. Procedure Set the environmental variable JAVA_HOME : USD export JAVA_HOME=jdk11 In VS Code, click the Extensions icon on the Activity bar to open the Extensions view. Enter Migration Toolkit for Applications in the Search field. Select the Migration Toolkit for Applications extension and click Install . The MTA extension icon ( ) is displayed on the Activity bar.

Commands:
export JAVA_HOME=jdk11
Chapter 6. Upgrading Identity Management Identity Management is generally updated whenever a system is upgraded to a new release. Upgrades should be transparent and do not require any user or administrative intervention. 6.1. Upgrade Notes Important Due to CVE-2014-3566 , the Secure Socket Layer version 3 (SSLv3) protocol needs to be disabled in the mod_nss module. You can ensure that by following these steps: Edit the /etc/httpd/conf.d/nss.conf file and set the NSSProtocol parameter to TLSv1.0 (for backward compatibility) and TLSv1.1 . Restart the httpd service. The update process automatically updates all schema and LDAP configuration, Apache configuration, and other services configuration, and restarts all IdM-associated services. When a replica is created, it must be the same version as the master it is based on. This means that replicas should not be created on an older bersion of Identity Management while the servers are in the process of being upgraded. Wait until the upgrade process is completed, and then create new replicas. Schema changes are replicated between servers. So once one master server is updated, all servers and replicas will have the updated schema, even if their packages are not yet updated. This ensures that any new entries which use the new schema can still be replicated among all the servers in the IdM domain. The LDAP upgrade operation is logged in the upgrade log at /var/log/ipaupgrade-log . If any LDAP errors occur, then they are recorded in that log. Once any errors are resolved, the LDAP update process can be manually initiated by running the updater script: Clients do not need to have new packages installed. The client packages used to configure a Red Hat Enterprise Linux system do not impact the enrollment of the client within the domain. Updating client packages could bring in updated packages for other dependencies, such as certmonger which contain bug fixes, but this is not required to maintain client functionality or behavior within the IdM domain.

Commands:
NSSProtocol TLSv1.0,TLSv1.1
service httpd restart
ipa-ldap-updater --upgrade
28.3. Logging to a Remote System During the Installation By default, the installation process sends log messages to the console as they are generated. You may specify that these messages go to a remote system that runs a syslog service. To configure remote logging, add the syslog option. Specify the IP address of the logging system, and the UDP port number of the log service on that system. By default, syslog services that accept remote messages listen on UDP port 514. For example, to connect to a syslog service on the system 192.168.1.20 , enter the following at the boot: prompt: 28.3.1. Configuring a Log Server Red Hat Enterprise Linux uses rsyslog to provide a syslog service. The default configuration of rsyslog rejects messages from remote systems. Warning Only enable remote syslog access on secured networks. The rsyslog configuration detailed below does not make use of any of the security measures available in rsyslog Crackers may slow or crash systems that permit access to the logging service, by sending large quantities of false log messages. In addition, hostile users may intercept or falsify messages sent to the logging service over the network. To configure a Red Hat Enterprise Linux system to accept log messages from other systems on the network, edit the file /etc/rsyslog.conf . You must use root privileges to edit the file /etc/rsyslog.conf . Uncomment the following lines by removing the hash preceding them: Restart the rsyslog service to apply the change: Enter the root password when prompted. Note By default, the syslog service listens on UDP port 514. The firewall must be configured to permit connections to this port from other systems. Choose System Administration Firewall . Select Other ports , and Add . Enter 514 in the Port(s) field, and specify udp as the Protocol .

Commands:
linux syslog= 192.168.1.20:514
USDModLoad imudp.so USDUDPServerRun 514
su -c '/sbin/service rsyslog restart'
Chapter 1. Red Hat Decision Manager Spring Boot business applications Spring Framework is a Java platform that provides comprehensive infrastructure support for developing Java applications. Spring Boot is a lightweight framework based on Spring Boot starters. Spring Boot starters are pom.xml files that contain a set of dependency descriptors that you can include in your Spring Boot project. Red Hat Decision Manager Spring Boot business applications are flexible, UI-agnostic logical groupings of individual services that provide certain business capabilities. Business applications are based on Spring Boot starters. They are usually deployed separately and can be versioned individually. A complete business application enables a domain to achieve specific business goals, for example, order management or accommodation management. After you create and configure your business application, you can deploy it to an existing service or to the cloud, through OpenShift. Business applications can contain one or more of the following projects and more than one project of the same type: Business assets (KJAR): Contains business processes, rules, and forms and are easily imported into Business Central. Data model: Data model projects provide common data structures that are shared between the service projects and business assets projects. This enables proper encapsulation, promotes reuse, and reduces shortcuts. Each service project can expose its own public data model. Dynamic assets: Contains assets that you can use with case management. Service: A deployable project that provides the actual service with various capabilities. It includes the business logic that operates your business. In most cases, a service project includes business assets and data model projects. A business application can split services into smaller component service projects for better manageability.

Commands:
Chapter 2. Power management auditing and analysis 2.1. Audit and analysis overview The detailed manual audit, analysis, and tuning of a single system is usually the exception because the time and cost spent to do so typically outweighs the benefits gained from these last pieces of system tuning. However, performing these tasks once for a large number of nearly identical systems where you can reuse the same settings for all systems can be very useful. For example, consider the deployment of thousands of desktop systems, or a HPC cluster where the machines are nearly identical. Another reason to do auditing and analysis is to provide a basis for comparison against which you can identify regressions or changes in system behavior in the future. The results of this analysis can be very helpful in cases where hardware, BIOS, or software updates happen regularly and you want to avoid any surprises with regard to power consumption. Generally, a thorough audit and analysis gives you a much better idea of what is really happening on a particular system. Auditing and analyzing a system with regard to power consumption is relatively hard, even with the most modern systems available. Most systems do not provide the necessary means to measure power use via software. Exceptions exist though: the ILO management console of Hewlett Packard server systems has a power management module that you can access through the web. IBM provides a similar solution in their BladeCenter power management module. On some Dell systems, the IT Assistant offers power monitoring capabilities as well. Other vendors are likely to offer similar capabilities for their server platforms, but as can be seen there is no single solution available that is supported by all vendors. If your system has no inbuilt mechanism to measure power consumption, a few other choices exist. You could install a special power supply for your system that offers power consumption information through USB. The Gigabyte Odin GT 550 W PC power supply is one such example. As a last resort, some external watt meters like the Watts up? PRO have a USB connector. Direct measurements of power consumption is often only necessary to maximize savings as far as possible. Fortunately, other means are available to measure if changes are in effect or how the system is behaving. This chapter describes the necessary tools.

Commands:
Chapter 8. Supported integration products AMQ Streams 1.8 supports integration with the following Red Hat products. Red Hat Single Sign-On 7.4 and later Provides OAuth 2.0 authentication and OAuth 2.0 authorization. Red Hat 3scale API Management 2.6 and later Secures the Kafka Bridge and provides additional API management features. Red Hat Debezium 1.5 Monitors databases and creates event streams. Red Hat Service Registry 2.0 Provides a centralized store of service schemas for data streaming. For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the AMQ Streams 1.8 documentation. Additional resources Red Hat Single Sign-On Supported Configurations Red Hat 3scale API Management Supported Configurations Red Hat Debezium Supported Configurations Red Hat Service Registry Supported Configurations

Commands:
Chapter 10. Hosts 10.1. Introduction to Hosts Hosts, also known as hypervisors, are the physical servers on which virtual machines run. Full virtualization is provided by using a loadable Linux kernel module called Kernel-based Virtual Machine (KVM). KVM can concurrently host multiple virtual machines running either Windows or Linux operating systems. Virtual machines run as individual Linux processes and threads on the host machine and are managed remotely by the Red Hat Virtualization Manager. A Red Hat Virtualization environment has one or more hosts attached to it. Red Hat Virtualization supports two methods of installing hosts. You can use the Red Hat Virtualization Host (RHVH) installation media, or install hypervisor packages on a standard Red Hat Enterprise Linux installation. Note You can identify the host type of an individual host in the Red Hat Virtualization Manager by selecting the host's name to open the details view, and checking the OS Description under Software . Hosts use tuned profiles, which provide virtualization optimizations. For more information on tuned , see the Red Hat Enterprise Linux 7 Performance Tuning Guide . The Red Hat Virtualization Host has security features enabled. Security Enhanced Linux (SELinux) and the firewall are fully configured and on by default. The status of SELinux on a selected host is reported under SELinux mode in the General tab of the details view. The Manager can open required ports on Red Hat Enterprise Linux hosts when it adds them to the environment. A host is a physical 64-bit server with the Intel VT or AMD-V extensions running Red Hat Enterprise Linux 7 AMD64/Intel 64 version. A physical host on the Red Hat Virtualization platform: Must belong to only one cluster in the system. Must have CPUs that support the AMD-V or Intel VT hardware virtualization extensions. Must have CPUs that support all functionality exposed by the virtual CPU type selected upon cluster creation. Has a minimum of 2 GB RAM. Can have an assigned system administrator with system permissions. Administrators can receive the latest security advisories from the Red Hat Virtualization watch list. Subscribe to the Red Hat Virtualization watch list to receive new security advisories for Red Hat Virtualization products by email. Subscribe by completing this form: https://www.redhat.com/mailman/listinfo/rhsa-announce

Commands: