Using Interactive Login for Troubleshooting with SSO Configured in Orchestrator

News Knowledge Base
, ,
1

Using Interactive Login for Troubleshooting with SSO Configured in Orchestrator.

Issue Description: Troubleshooting with Single Sign-On (SSO) configured in Orchestrator using Interactive Login can encounter challenges if not set up properly. Ensuring a seamless troubleshooting session requires meeting specific conditions related to SSO configuration, user access, and session initiation.

Resolution: Conditions for Seamless Interactive Login Troubleshooting,

  1. SSO Integration:

  • Verify that the Orchestrator’s SSO configuration is correctly set up and operational. This includes ensuring that the identity provider (e.g., Azure AD) is properly linked to your Orchestrator.

  1. Interactive Login Access:

  • During troubleshooting, the user will manually enter their credentials. With SSO configured, this typically means they will be redirected to the SSO login page for authentication.

  1. Session Initiation:

  • Once authenticated through SSO, the troubleshooting session should begin without issues. It is crucial that the authentication method (SSO) remains consistent even when initiated interactively.



Steps for Configuring a Troubleshooting Session with Interactive Login:

  1. Verify SSO Configuration: Ensure that your SSO setup in Orchestrator is functioning correctly.
  2. Initiate Interactive Login: Access the Orchestrator's login page.

    • Select the option for interactive login, which will typically redirect to the SSO provider for authentication.

  3. Authenticate via SSO: Complete the SSO login process, which may include entering credentials and possibly multi-factor authentication (MFA).
  4. Begin Troubleshooting: Once logged in, it should be possible to access the necessary areas for troubleshooting.



Key points to remember:

  1. Consistency in Authentication: Ensure that the SSO method used for regular access is the same during the interactive troubleshooting session to avoid conflicts.
  2. User Permissions: Ensure that the troubleshooting user has appropriate permissions configured in Orchestrator to perform the necessary tasks.
  3. Logging and Auditing: Make sure that the Orchestrator logs these interactive sessions appropriately for audit purposes.