Constraints and Limitations
The following constraints apply when using Grid SSO:
| • | You must enable cookies in your browser. |
| • | When a Primary Director fails, the Grid SSO session is lost. If you have a Secondary Director configured for failover, you can log in to it and start a new SSO session. |
| • | Single sign-on enables you to log in to other Managers that are in the same network subdomain. For example, if your Primary Director is director.grid.example.com, logins to any Brokers in grid.example.com can be authenticated with Grid SSO. You can’t use Grid SSO to connect to Brokers in other subdomains or domains. For example, if your Primary Director is director.grid.example.com, you can’t automatically log in to Brokers in prod.example.com or grid.example.co.uk. |
| • | Only the following fields accept multi-byte characters: |
| — | Username, Password, and Confirm Password on the initial login page. |
| — | All fields on the Admin > User Admin > Run-As Credentials page. |
| — | Choose Username on the User Event page. |
| — | Username, Firstname, Lastname, Password, and Confirm Password on the Users > Users page. |
| — | RunAsUser on the Edit Service Type page. |
| • | Grid SSO must not be used if Negotiate Authentication is used. |