AnsweredAssumed Answered

Kerberos Share SSO  - trying out whats new in HEAD

Question asked by loftux on Jun 15, 2010
Latest reply on Oct 29, 2013 by jean-rémyrevy
I'm trying to set up the new SSO mechanism found in HEAD that will support Kerberos SSO for Share.
And of course there is a lot of guesswork when playing with the latest stuff  :)

I'm getting this error
12:11:11,580 WARN  [] credentials can not be delegated!

So I made sure the accounts set up kerberos for had the setting "trusted for delegation" ticked in AD. Didn't help.
in krkb5.conf i have
        forwardable = true
        proxiable = true

This is what I have in share-config-custom.xml
   <config evaluator="string-compare" condition="Remote">
           <name>Alfresco Connector</name>
           <description>Connects to an Alfresco instance using cookie-based authentication</description>
           <name>Alfresco - user access</name>
           <description>Access to Alfresco Repository WebScripts that require user authentication</description>

Should I use alfrescoCookie as connector-id? The server endpoint-url uses the same server-name as for the security principals.

As for the Share Kerberos config
   <!– Kerberos settings –>
   <config evaluator="string-compare" condition="Kerberos" replace="true">
I re-used the Config for Alfresco Explorer, is that allowed?
I tried to create a separate keytab for Share, but since HTTP/ was and they are on the same server, I used HTTPSHARE/ for the user created. Didnt work.
Is there a rule that the prefix for HTTP application must be exactly that? If so, then my understanding is that the only way to get this setup to work is to setup Share and Alfresco on separate servers.