Disable the use of ServiceNow "Login Rules" as an authentication method for vRA plugin

[GigaDuck]

We are seeing delays of 15 seconds for the ServiceNow homepage to load when someone is "vra_user" due to the vra plugin always pushing us to authenticate with vRA.

The plugin is pushing us to authenticate with vRA regardless if we are accessing a vRA resouce (authentication happens only once and at the beginning of a new ServiceNow session).  As this happens almost always when people are trying to access the standard ServiceNow homepage.... people are incorrectly assuming that ServiceNow is running slow.

We have troubleshooted this issue due to the use of "Login Rules" by the plugin within the ServiceNow system. Is there any way to prevent the authentication until someone is trying to access the vRA catalog? More importantly, ServiceNow has deprecated the use of "Login Rules" for some time (please see the links below from archive.org , the new documentation site for ServiceNow no longer has this info readily available).

Configuring the Login:

https://web.archive.org/web/20170208224027/wiki.servicenow.com/index.php?title=Legacy:Configuring_th...​

Content Management Security:

https://web.archive.org/web/20150122092812/http://wiki.servicenow.com/index.php?title=Content_Manage...

Configuring the Login Screenshot:

Content Management Security:

[draymond10]

I've always seen this delay; VERY ANNOYING.  Hard to believe the SSO handshakes take this long.  I'm sure you could write a business rule to execute on Selection of vRA Catalog Item that would kick off the authentication.  Sorry not a ServiceNow developer or I'd give you more details. We worked around this by removing everyone from vra_users and utilized a single service account.  All entitlements/requests go through as a single service account.  If you need to change ownership of the VM at the end, use vCO.

[CalsoftTechie]

@GigaDuck - We already gone through this and as per serviceNow Login rule deprecated but not obsolete.

We had a POC where we implemented login redirection some other way but it had some limitations wrt Customers existing modules on ServiceNow platform so dropped that idea as it was not unique across all customers.

We will let you know once any other workaround is implemented in this case.