Thanks for the fast reply.
Now I have read some other blog entries from SAML user. Maybe I have a misunderstanding about the SAML integration in nextcloud.
I have two seperated user directories for different applications and usages.
In both directories are the same user (person) but with other IDs (username, passwords,rights …)
I wanted to use the SAML function to map the user from directory A with the user from directory B (same person). Like the ADFS function in Office365. I thought: if a user is still authenticated in directory A he get access via SAML/SSO to his mapped nextcloud user from directory B.
What I have done:
So I activated the LDAP plugin in nextcloud and created a LDAP connection to directory B for the user creation in nextcloud.
At this point all was working fine. I could login at nextcloud by input username and password from user in directory B. By activating SAML Plugin I realized that I couldn’t create new “local” nextcloud user and also no new created LDAP user in directory B appeared in nextcloud database.
When I disable the SAML Plugin, all is working as before.
So I think there must be a design failure in my scenario?!
One more question:
Do you have any information about the apps? Are these apps full SAML integrated (iOS, Android, desktop)
Please let me know - where my failure could be … !!