Automic Workload Automation

 View Only
Expand all | Collapse all

AWI: option to preserve connection parameters in URL in browswer

  • 1.  AWI: option to preserve connection parameters in URL in browswer

    Posted Sep 18, 2023 07:01 AM
    Edited by Michael A. Lowry Sep 18, 2023 07:57 AM

    I submitted a new idea that would be helpful to Automic Automation shops that use single sign-on.

    AWI: option to preserve connection parameters in URL in browser 

    Background

    When the AWI environment variable AUTOMIC_PARAMETER_LOGIN_ENABLED is set to true, AWI users may provide URL parameters to facilitate automatic login with single sign-on.

    For example, the user could provide the department, logintype, and autologin parameters as in the following example:

    https://awi.mycorp.com/awi/AE_PROD/0001@pa?department=MYCORP&logintype=SAML&autologin=true

    However, once the user has logged in, the AWI removes the connection parameters from the URL displayed in the URL field. ...

    https://awi.mycorp.com/awi/AE_PROD/0001@pa


    ...



    [The AWI should not remove connection parameters from the URL, because URLs lacking these parameters cannot be used to transparently log in using single sign-on.]



    ...

     

    Proposal

    If the AUTOMIC_PRESERVE_CONNECTION_PARAMETERS environment variable is set to true, the AWI will preserve at the end of the URL displayed in the browser any connection parameters provided when initially establishing the AWI session. All AWI browser windows/tabs associated with this  AWI session will have these connection parameters (department, logintype, and autologin) at the end of the URL displayed in the browser..

    If you like the idea, please vote for it.



  • 2.  RE: AWI: option to preserve connection parameters in URL in browswer

    Posted Sep 18, 2023 07:35 AM
    Edited by Michael A. Lowry Sep 18, 2023 08:43 AM

    I also submitted another complementary idea:

    AE: Department-specific default AWI connection parameters.

    Proposal

    The Automation Engine should provide a mechanism whereby administrators can define default AWI connection parameters on a per-department basis. When an administrator has defined defaults for a department, all connections to the AWI from a user in that department will implicitly include these default parameter values.

    Example

    The department CORP is configured to use SAML for single sign-on. The AE administrator creates the static VARA object UC_AWI_DEFAULT_PARMS_CORP in client 0 and then specifies thew following default AWI connection parameters in this VARA object.

    UC_AWI_DEFAULT_PARMS_CORP

    Key Value 1
    autologin true
    department CORP
    logintype SAML

    With the above object defined in client 0, the AWI transparently adds the specified parameters to all URL-based logins for any user in department CORP, if these parameters are not present in the URL provided by the user.

    The AWI does not override parameters specified by the user in the URL and does not override parameters provided via the login window.

    The two ideas address the same need but could could be implemented independently.