Caveat: I’m not a Domino admin, so may have missed something obvious.
Domino Server 7
Authenticating with the Domino Directory.
Trying to set up SSO with WebSphere, although that doesn’t yet come into play. I have already successfully set the WebSphere code to initiate the authorization, sending the token implicitly along to the session create. Here, trying to have Domino prompt for authorization so I can capture the LtpaToken later on.
Created Web Internet Site doc (the only one, there is a IIOP doc).
Filled in the Name and Organization
Made this the default site
Set ‘Session Auth’ to "Multiple Servers’
If I refresh HTTP, it complains that the SSO config is invalid. However, I can access a database on the server, get prompted for a login, and be successfully redirected to the db. However, the cookie shows DomAuthSessId, not LtpaToken (as expected).
So then I create a Web SSO doc.
Name = ‘LtpaToken’
Filled in Organization and DNS Domain
Selected Keys > Create Domino SSO key
Updated Web Site doc to point to the LtpaToken SSO doc. Refreshing HTTP usually still notes that the SSO config is invalid. Once it was accepted, but not sure why. When it is, then when I authenticate at the login page, it never redirects me to the actual database, it just returns an empty login page. I know I’ve authenticated, because an invalid id or password will generate the expected error message. And when I got to that point, the cookie still said DomAuthSessId, not LtpaToken.
Am I missing something fundamental in the config?