Versions Compared

Key

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

...

  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

      2. If login is not sucessful 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. Update default administration application access policy - NOTE that this service will be named Standalone Yarnman Administration App by default

    2. 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

Yarngate Configuration

Info

This section assumes that that Yarngate access has been configured and the user can login to Yarngate using LDAP credentials

Info

This section assumes that Customers/Clusters/Interfaces have been added either manually via the administration application or via Bulk import of Customers/Cluster/Interfaces