[ 
http://opencast.jira.com/browse/MH-8577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29320#comment-29320
 ] 

Adam McKenzie commented on MH-8577:
-----------------------------------

Hi Hank,

I just wanted to let you know that when we implemented CAS & LDAP for 1.3 / 
Trunk we ran into some missing code from 1.2: 
http://opencast.jira.com/browse/MH-8580

So if you use trunk at least revision 11839 or greater I think at least for 
authorization it should hit your LDAP server, I still need to look at 
authentication using LDAP in Spring security. Right now if you set the admin 
user in the config.properties file to a user you expect in the LDAP directory 
such as:

org.opencastproject.security.demo.admin.user=akm220
org.opencastproject.security.demo.admin.pass=opencast

instead of:
org.opencastproject.security.demo.admin.user=admin
org.opencastproject.security.demo.admin.pass=opencast

It should let you into the matterhorn admin ui as administrator and if you look 
at /info/me.json it should have all of the LDAP roles you expect. I will need 
some more time to figure out LDAP authentication.

Cheers,
Adam
                
> LDAP Authentication
> -------------------
>
>                 Key: MH-8577
>                 URL: http://opencast.jira.com/browse/MH-8577
>             Project: Matterhorn Project
>          Issue Type: Bug
>          Components: Architecture & Services
>    Affects Versions: 1.3
>            Reporter: Hank Magnuski
>            Assignee: Adam McKenzie
>            Priority: Critical
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[email protected]
_______________________________________________

Reply via email to