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

Confirm we have the right LDAP permissions enabled #336

Open
cbeer opened this issue Jul 30, 2019 · 5 comments
Open

Confirm we have the right LDAP permissions enabled #336

cbeer opened this issue Jul 30, 2019 · 5 comments
Assignees

Comments

@cbeer
Copy link
Member

cbeer commented Jul 30, 2019

I was expecting to see eduPersonEntitlement available on -uat (see #335), but no such luck. I wonder if something got lost in translation from webauth/ldap to shibboleth attributes?

@tallenaz
Copy link
Contributor

See https://github.com/sul-dlss/operations-tasks/issues/1930 for the source of the HELPSU request
and also some docs around eduPersonEntitlement: https://uit.stanford.edu/service/saml/arp

@tallenaz tallenaz self-assigned this Jul 30, 2019
@tallenaz
Copy link
Contributor

From some discussion with the rest of ops: for eduPersonEntitlement it depends on whether we're using an LDAP query for that attribute, or looking to the SAML headers. If the former, we'll have to issue another UIT request. If the latter, the attribute should be already released.

@tallenaz
Copy link
Contributor

We can get access to eduPersonEntitlement, via shib headers, but only relative to particular workgroup stems or sub-stems, and we don't want to restrict ourselves that way here.

Since we want broader access, we might be able to do LDAP lookups with a keytab in the app. If we went that way, we'd have to write code to do that, and get a ticket in to UIT to request the keytab.

@cbeer
Copy link
Member Author

cbeer commented Jul 31, 2019

The things we need from eduPersonEntitlement are the same things we're already getting with stacks, requests, or many of our other apps. I'm not sure why we can't get them out of the header the same way?

@camillevilla
Copy link
Contributor

Note from post-planning meeting:

Sponsored SUNet accounts get a “Unable to authenticate” message, but we should use LDAP priv group to (1) figure out who they are (2) give them a clearer message

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

3 participants