Single sign on

I have found the answer - when I wasn't looking for it.

The answer is to do what I have been doing, i.e. modify the login.xsl page - as suggested in this kb article:

http://kb.adobe.com/selfservice/viewContent.do?externalId=9eb26121&sliceId=1

Stoners

It is possible to use the API when you have the users password - all I have is their network credentials, from which I query Active Directory to get their saMAccountName property (which is the ext-login) for the users. I can then set up Connect to accept a custom header property which I set to be the saMAccountName and the system logs me in and returns the BreezeSession cookie fine.

My real issue is with not allowing users to browse to the home page of the Connect box to stop them seeing the connect log in screen (this also applies when users access meetings / content etc directly through urls which will also show them the sign on if the content is not public).

I have managed to do this by altering the login.xsl page and applying a redirect in there - but there must be a better solution???

There is an xsl-variable attribute in the file called 'login-redirect' which if set will perform the redirect also, but I cannot find where to set this variable.

Any ideas???

Hi. would it be an option to use xml apis to login your users from your custom page?
hi
francesco