Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 2. Logging in to self-service automation portal
2.1. Signing in to self-service automation portal Copier lienLien copié sur presse-papiers!
Prerequisites
- You have configured an OAuth application in Ansible Automation Platform for self-service automation portal.
- You have configured a user account in Ansible Automation Platform.
Procedure
In a browser, navigate to the URL for self-service automation portal to open the sign-in page.
- Click .
The sign-in page for Ansible Automation Platform appears:
- Enter your Ansible Automation Platform credentials and click Log in.
- The self-service automation portal web console opens.
Troubleshooting
If you are using custom or self-signed SSL certificates and when attempting to log in to self-service automation portal, it displays the error:
Login failed; caused by Error: Failed to send POST request: fetch failed
This error indicates that self-service automation portal cannot verify the SSL certificate from your Ansible Automation Platform instance.
To resolve this issue, configure self-service automation portal to trust your custom CA certificate. For more information, see Section 2.2, “Configuring custom SSL certificates for self-service automation portal”.
While you can disable SSL validation by setting checkSSL: false in the Helm chart configuration, this approach is not recommended for production environments as it reduces security. Instead, configure self-service automation portal to trust your custom CA certificate.
2.2. Configuring custom SSL certificates for self-service automation portal Copier lienLien copié sur presse-papiers!
If your Ansible Automation Platform instance uses custom or self-signed SSL certificates, you must configure self-service automation portal to trust those certificates. Without this configuration, authentication between self-service automation portal and Ansible Automation Platform fails with SSL verification errors.
Prerequisites
- You have administrator access to your OpenShift Container Platform cluster.
- You have the custom Certificate Authority (CA) certificate file used by your Ansible Automation Platform instance.
- self-service automation portal is installed in your OpenShift Container Platform cluster.
Procedure
Obtain the CA certificate file from your Ansible Automation Platform instance.
If you do not have the CA certificate file, you can extract it from your Ansible Automation Platform server:
openssl s_client -showcerts -connect <aap-hostname>:443 </dev/null 2>/dev/null | openssl x509 -outform PEM > aap-ca-cert.pemReplace
<aap-hostname>with your Ansible Automation Platform hostname.- Log in to your OpenShift Container Platform cluster with administrator privileges.
Create a ConfigMap containing your custom CA certificate:
oc create configmap custom-ca-bundle \ --from-file=ca-bundle.crt=aap-ca-cert.pem \ -n <namespace>Replace
<namespace>with the namespace where self-service automation portal is installed.Update your self-service automation portal Helm chart values to mount the custom CA certificate:
upstream: backstage: extraEnvVarsSecrets: - custom-ca-bundle extraVolumes: - name: custom-ca configMap: name: custom-ca-bundle extraVolumeMounts: - name: custom-ca mountPath: /etc/pki/ca-trust/source/anchors/ readOnly: trueApply the updated configuration by upgrading the self-service automation portal Helm chart:
helm upgrade <release-name> <chart-name> \ -f values.yaml \ -n <namespace>Replace
<release-name>with your Helm release name and<chart-name>with the self-service automation portal chart name.- Wait for the self-service automation portal pods to restart with the new configuration.
Verification
Verify that the self-service automation portal pods are running:
oc get pods -n <namespace>All self-service automation portal pods should show a status of
Running.Attempt to sign in to self-service automation portal using your Ansible Automation Platform credentials.
If the SSL certificate configuration is correct, you can authenticate successfully without SSL verification errors.
Check the self-service automation portal logs for SSL-related errors:
oc logs -n <namespace> <pod-name> | grep -i sslIf you see no SSL verification errors, the custom CA certificate is trusted correctly.
Troubleshooting
If you continue to experience SSL verification errors after following this procedure:
- Verify that the CA certificate file contains the complete certificate chain.
- Ensure that the certificate file is in PEM format.
- Confirm that the Ansible Automation Platform hostname in your configuration matches the hostname in the SSL certificate.
-
Check that the
checkSSLparameter in your Helm values is set totrue(the default). Setting it tofalsedisables SSL verification entirely, which is not recommended for production environments.
2.3. Viewing templates Copier lienLien copié sur presse-papiers!
Prerequisites
- You have signed in to self-service automation portal.
Procedure
- In a browser, sign in to self-service automation portal.
In the navigation pane, select Templates to open a landing page where tiles are displayed, representing the templates that you have access to.
2.4. Synchronizing auto-generated templates Copier lienLien copié sur presse-papiers!
The auto-generated self-service templates are synchronized from the job templates in Ansible Automation Platform to self-service automation portal. You can manually trigger a sync from the Templates page.
This synchronization fetches updates for auto-generated self-service templates only.
Procedure
- In a browser, sign in to self-service automation portal.
In the navigation pane, select Templates to display the templates that you have access to.
- Select Sync now to launch a synchronization.
2.5. Viewing task run history Copier lienLien copié sur presse-papiers!
You can view a list of all the tasks that have been run from self-service automation portal. You can manually trigger a sync from the Templates page.
Procedure
- In a browser, sign in to self-service automation portal.
In the navigation pane, select History.
The Task list page displays the tasks that have been run.
Troubleshooting
If the Task List page does not display the tasks that have been run, contact your administrator to ensure that the scaffolder.task.read permission is selected in RBAC for your account.