...
Add the yarngate application service
Configure the yarngate services
Configure service name
Select node/arm
Host should use localhost as yarngate will be behind the proxy service
HTTPS can remain default
Select Authentication policy configured previously for Yarngate
Open the Proxy Service
Select proxy service - service routing
Add the yarngate application and save
Test Access to Yarngate using the LDAP authentication policy
Copy the base path - this will be randomly generated /yarngate-app-16a85c5e89e142e5bebaa547bc5eeda5
Logout of yarnman
browse to the yarngate application https://<yarngate IP address>/<base url>
Example https://<yarngate IP address>/yarngate-app-16a85c5e89e142e5bebaa547bc5eeda5
The login prompt should appear
If login is sucessful
proceed to next step
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
Finalise LDAP configuration
Update default administration application access policy - NOTE that this service will be named Standalone Yarnman Administration App by default
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 |