NuKVM/xen-orchestra
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
62c3fa13ca6c142df179fa0f999a01e83eb14bf0
xen-orchestra/docs/authentication.md
Jon Sands 0045a1e608 Lucky #13 (grammar updates) (#135) 
* Clarification, update links, organize

* add nfs warning, fix debian version

* add ENOSPC troubleshooting

* add more enospc detail

* add note on editing username

* Documentation typo/grammar cleanup part 9

* grammar cleanup v10

* grammar editing v10

* grammar updates v11

* Grammar updates v11

* Lucky #13 (grammar updates)
2018-05-22 00:00:19 +02:00

1013 B
Raw Blame History

User authentication

Xen Orchestra supports various types of user authentication, internal or even external thanks to the usage of the Passport library.

There are 2 types of XO users:

  • admins, with all rights on all connected resources
  • users, with no rights by default

All users will land on the "flat" view, which displays no hierarchy, only all their visible objects (or no object if they are not configured).

ACLs will thus apply only to "users".

Any account created by an external authentication process (LDAP, SSO...) will be a user without any permission.

Also, you don't have to create an external user by yourself: it will be created automatically in Xen Orchestra after its first connection.

Debugging

If you can't log in with your LDAP/SAML/Github/Google settings, please check the logs of xo-server while you attempt to connect. It will give you hints about the error encountered. You can do that with a tail -f /var/log/syslog -n 100 on your XOA.