Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(feature) Together with keystone #70

Closed
cbartz opened this issue Oct 21, 2014 · 1 comment
Closed

(feature) Together with keystone #70

cbartz opened this issue Oct 21, 2014 · 1 comment

Comments

@cbartz
Copy link
Contributor

cbartz commented Oct 21, 2014

It would be nice if swauth could be used with keystone at the same time, because keystone does not provide local users within an account (all users are global). The creation of external users (which do not have to be stored in the keystone database / ldap) would be easily doable.

A quick solution is to add in line 195 in middleware.py:

    if 'keystone.identity' in env:
        return self.app(env, start_response)
@gholt
Copy link
Owner

gholt commented Dec 22, 2014

Seems fine to me. The previous thought behind the two or more auth systems use case was that each would use different reseller prefixes, but I suppose this would allow Keystone and Swauth to use the same prefixes. It could get confusing when tracking logs and usage trying to determine which system authorized which request; but that should only be a problem with those that configure their systems to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants