Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

It is assumed that yarnman has been deployed and installed as per Yarnman Installation and Setup for standalone install

Note that the authentication setup requires specific configuration for Yarngate

...

  1. Add the yarngate application service

  2. Configure the yarngate services

    1. Configure service name

    2. Select node/arm

    3. Host should use localhost as yarngate will be behind the proxy service

    4. HTTPS can remain default

    5. Select Authentication policy configured previously for Yarngate

  3. Open the Proxy Service

  4. Select proxy service - service routing

  5. Add the yarngate application and save

  6. Test Access to Yarngate using the LDAP authentication policy

    1. Copy the base path - this will be randomly generated /yarngate-app-16a85c5e89e142e5bebaa547bc5eeda5

    2. Logout of yarnman

    3. browse to the yarngate application https://<yarngate IP address>/<base url>

      • Example https://<yarngate IP address>/yarngate-app-16a85c5e89e142e5bebaa547bc5eeda5

    4. The login prompt should appear

    5. If login is sucessful

      1. proceed to next step

        Image RemovedImage Added
      2. If login is not sucessful successful refer to the following LDAP authentication troubleshooting guide LDAP Authentication and Authorisation Troubleshooting or raise a support case including the yarnman logs to resolve before proceeding

  7. Finalise LDAP configuration

    1. Before completing step b. below, it is important to complete one of the following not to lock yourself out of the Administration Application

      1. Create a second administration application as flagged in warning note at the beginning of this section. Process for this may be found here Adding Secondary Local Auth Administration Access

      2. Give Administration Application access to one of the roles created earlier. Open Database created earlier, select Roles, then under Administration Tab, check the app access check box for the required role.

    2. Update default administration application access policy - NOTE that this service will be named Standalone Yarnman Administration App by default

    3. Optionally set the yarngate application to be the default application for the proxy so that when users browse to yarngate and login they will go directly to Yarngate