Non-web Clients

[lalith jayaweera]

 When setting up Shibboleth with Basic Http authentication for ECP, to check Office365, is it correct to state login 'username' will be email. Hence in the apache block for the ECP,  the AuthLDAPURL will be something like below.
 
AuthLDAPURL ldap://ldap.example.org/ou=People,dc=example,dc=org?mail

because Looking at lot of non-web thick clients, e.g. Office365 clients, outlook profiles,  etc.
 
they all start with email address as the username during the set up progress, because I did not get any hit to the IdP server at all.
 
Issue is our current Web SSO is, the username is 'UID' (staffId) not email address. Is it possible to facilitate both?
 
Would like to know your thoughts on this.
 
After setting up ECP and Windows Azure side, we tried to Test the Office365 ECP integration on a real mobile device(iPhone), that is, I tried to add a account of type exchange using the native mail client app in iPone6, but it failed. I am having doubts whether it is to do with no email username for login in ECP. Because setup starts asking for the with email.
 
This is the case even you try to create a mail profile.
 
As the first thing, I would like to have a hit to IdP from the mobile device regardless success or failure.
 
 
Thanks
 
 
 
 
 
 
 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150730/7f9c1803/attachment.html>