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.

Sign up for GitHub

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

Jump to bottom

Require Configured SOR Only #28

Open
boshrin opened this issue Aug 6, 2014 · 0 comments
Open

Require Configured SOR Only #28

boshrin opened this issue Aug 6, 2014 · 0 comments
Milestone
FUTURE

Comments

@boshrin
Copy link
Owner

boshrin commented Aug 6, 2014

Currently, the match engine will allow any value for SOR, assuming the client is authorized for it. So if a client is authorized for '*', it might send 'sis', 'SIS', or 'student' all meaning the same thing. Perhaps require SORs to be defined in the [sors] section of config.in. This could then allow 'sis' while rejecting the other 2 as undefined.
@boshrin boshrin added this to the FUTURE milestone Aug 6, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
FUTURE
Development

No branches or pull requests
1 participant
@boshrin