I am trying to set up SSO on one server but I am running into some problems. I followed the documentation but i cannot get the SSO to load. Upon starting the server i do not receive an error message and I do not receive a message stating that SSO loaded successfully.
When i try to access the server i get prompted for login as usual but i cannot login. When i submit my credentials it seems like it just reloads the login page. If i specify the wrong password i will get the invalid password notification so i know that it is at least verifying the login… Anyone have a clue what i might be doing wrong?
Do you have two tier domains? If not, try creating another domain in your DNS…
I’ve spent the whole day on this. Having a correctly setup SSO generates no message. To get a message, I set “Internet Protocols\Domino Web Engine\Web SSO Configuration” to blank on the server document. The following message then appears after restarting HTTP
“HTTP Server: No Web SSO Configuration specified, using default (‘LtpaToken’)”
So I know its working.
A crucial part of SSO is the domain name. I have a single level domain here called “Blueprint” - we are a small company and everything fits in it. Consequetly I had a “Web SSO Configuration” document with the DNS Domain set to “.blueprint”.
When I then accessed my Domino server by the FQDN “piccadilly.blueprint”, I kept getting the username and password prompt over and over again like a bad game of two up. All the postings on this site pointed to the fact that you can get this thing to work, but everbody has two tier domains - so I created a new domain called Test with a host document in it for piccadilly.
I changed the DNS in the “Web SSO Configuration” to “.test.blueprint”. I can now access domin server as “piccadilly.test.blueprint”, and hey presto, 8 hours later, its working.