So basically two questions: why does o365 rject my password. Checked at ucs and login is possible?
How to assign other licenses than student?
How to define groups in UCS that will be given to o365?
You can set the UCR variable office365/groups/sync to yes and restart the univention-directory-listener service to enable group sync. Once a user group is modified it is checked if it should be synced to the Azure AD.
hi,
thanx for the UCR hint - I always forget to check this first
At https://login.microsoftonline.com/ I get “account or password is not correct”. here I use the email adress instead of the the UCS username (username is something like asb123 email is User Principal Name (ab.12@test.de)
On O365 login is allowed for this user and licenses are assigned. And when I set a new password at O365 admin center login is possible. Seems O365 is not able to use my UCS to log me in.
The key concept for the connector is that the user password does not leave the UCS domain. This has the consequence that we do not sync passwords into the Azure cloud.
Therefore, Single Sign-On has to be used with the Office365 connector. The wizard describes the required steps to configure the Azure AD for Single Sign-On.
thanx for confirmation that I understood O365 connector right…
however, even though I followed the wizard, I can’t log in. Maybe one remark: the laptop / computer is NOT part of the domain and just using the web interface from O365 to log in. Is O365 only working for clients in the domain?
Or do you have an idea where to start debugging? At the end we need a solution that will use UCS for O365 login just like we have for NextCloud too…
Using the Office365 services is possible from any computer that can access the Office365 website as well as the UCS Single Sign-On loginpage. The computer does not have to be joined into the UCS domain.
If i understood you correctly, after entering the username at the Microsoft loginpage, you can also enter your password on that page. The user should get redirected to the UCS Single Sign-On login. If that is not the case, it indicates that the powershell script offered by the wizard has not been run or has not run successfully.
Open the setup wizard again, there is a button to get to the page where the configuration of Single Sign-On is described.