Issue by byrman
Monday Aug 24, 2015 at 14:43 GMT
Originally opened as https://github.com/nens/lizard-nxt/issues/1037
If a user logs on via the web client, his organisations and roles are fetched from the SSO server. This is not true when using the API directly. This may be a problem for suppliers/systems that never use the GUI.
Steps to reproduce the problem:
- Choose a test user on your portal.
- Delete the corresponding records in lizard_auth_client_userorganisationrole.
- On the SSO server, make sure that the test user is a member of at least one organisation.
- Log in to your portal via the API (you can use the link provided by the Django REST framework).
- Inspect lizard_auth_client_userorganisationrole and notice that there are no records for test user.
Compare this behaviour to:
- Choose a test user on your portal.
- Delete the corresponding records in lizard_auth_client_userorganisationrole.
- On the SSO server, make sure that the test user is a member of at least one organisation.
- Log in to your portal via the GUI (i.e. lizard-client).
- Inspect lizard_auth_client_userorganisationrole and notice that there are records for test user.
Monday Aug 24, 2015 at 14:43 GMT
Originally opened as https://github.com/nens/lizard-nxt/issues/1037
If a user logs on via the web client, his organisations and roles are fetched from the SSO server. This is not true when using the API directly. This may be a problem for suppliers/systems that never use the GUI.
Steps to reproduce the problem:
Compare this behaviour to: