Hey Dimitar,
Thanks for responding. Sorry I didn't make it clearer, but yes, the Redwood CPS login uses the same mechanism as NWA, useradmin which in my case, are both tied to Microsoft AD. Before I had enabled SSO via SPnego, I logged in with my AD credentials to all of those: NWA, useradmin, Redwood CPS.
After SPnego, it's all SSO. But I can use the "?spnego=disabled", in the NWA/useradmin URL to force a login, but not for Redwood CPS. But again, it's just a URL, nothing fancy.
That other thing you said about changing the header, sounds neat, but I don't really know what to do. When you say "use HTTP header x-sap-spnego: disabled" I don't know what to do with that.
I'm not getting into any of that "risk based" stuff. I don't need this any more complicated that it already is, but thanks for saying that.
As far as that help link goes for "tshw", I followed that. select incident "Authentication".
then reproduced with the ....50000/scheduler?spnego=disabled
Here's what I found:
Then,
So yes, I did get a " LOGIN.OK" string and the application is using SPnego.
But again, it seems to be ignoring the "?spnego=disabled" and I really just want that to work.
NICK