2 of 2 people found this helpful
Step-1: Understand the type of SAML Implementation like IDP
- The customer provides IdP metadata (which defines the URLs used by the customer for SAML, and certificate used for validation of assertions).
Step-2: Acquire the Metadata Files
- The metadata is provided to allow the customer to pre-register the Service Provider in their SAML infrastructure as required.
Step-3: Configure SAML and Atrium SSO
- Modify the Atroum SSO login and logout URL
Step-4: Restart the Midtier Services
There are several types of Authentication Methods
- Standard authentication
- LDAP pass-through (AREA LDAP)
- Federated AREA SSO
- Federated SAML
- LDAP pass-through (Atrium SSO)
This will help a lot,
I know that once we have Atrium SSO, we need to login only once and no need to authenticate all other BMC Products.
Will that apply with SAML as well.
I want user to authenticate only once when they login to Windows machine and when they click on any Remedy URL it should not ask for login again,
Do you think it can be achieved with using Atrium SSO with SAML?
Yes, Federated SAML is for all products.
So If I integrate SSO with SAML, will it still open Atrium Login Page for authenticaion or
it will redirect to application as I already authenticated when I logged on my machine.
just to confirm and be super clear, you are saying that the SAML integration is full "transparent" the same as Kerberos - therefore no login to the SSO Server is required?