Configuring ASSO with IDP initiated SAML integration

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Atrium Single Sign On


    APPLIES TO:

    BMC Atrium Single Sign On



    PROBLEM:

     

    How to integrate Atrium SSO (ASSO) with SAML using IDP initiated login.
     

     


    CAUSE:

    NA


    SOLUTION:

     

    Most of our customers use SP initiated login process, which works fine with all internal embedded links. This customer wanted to use IDP initiated login process.

    Usually in SP initiated login, ASSO checks the user validity and forwards the request to IDP for login.

    In SP initiated process, users login first to IDP using their standard login screen and after that IDP posts the SAML response to ASSO.

    In IDP initiated login you still need to do the IDP configuration and SP configuration as usual. Instead of typing

    http://MID_TIER/arsys

    customers will type a different url that will take them to IDP login screen. e.g.,

    https://<IDP_LOGIN_URL>?PartnerSpId=RemedyQA_SP&TARGET=MidTierURL

    IDP_LOGIN_URL is URL of the login link. Provided by customer's IDP team
    PartnerSpId=Parameter for IDP login URL. This can change from customer to customer. The value of this parameter is the name of Service Provider you define in ASSO.
    TARGET=Name of the parameter, whose value will be the MidtierURL. Name of parameter can change from customer to customer. Value of this parameter is mid tier url. e.g., http://mid_tier_host_name:8080/arsys


     

     


    Article Number:

    000080698


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles