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

Status van CO (active/expired) in ldap #81

Closed
baszoetekouw opened this issue Feb 24, 2023 · 6 comments · Fixed by #129
Closed

Status van CO (active/expired) in ldap #81

baszoetekouw opened this issue Feb 24, 2023 · 6 comments · Fixed by #129
Milestone
v31

Comments

@baszoetekouw
Copy link
Member

No description provided.

@baszoetekouw
Copy link
Member Author

Zie ook SURFscz/SRAM-deploy#498

@baszoetekouw baszoetekouw moved this from New to Todo in SRAM development Feb 24, 2023
@baszoetekouw
Copy link
Member Author

Nu worden de users van een expired CO allemaal individueel als expired getoond (https://github.com/SURFscz/plsc/blob/main/sbs.py#L185-L188). Dat is niet echt praktisch voor diensten.

@baszoetekouw baszoetekouw self-assigned this Feb 24, 2023
@mrvanes
Copy link
Contributor

mrvanes commented Jan 12, 2024

En wat is dan precies de bedoeling?

@baszoetekouw
Copy link
Member Author

We moeten een expired attribuut op de CO zetten denk ik (en/of de nbijbehorende groepen), niet op de persoon

@mrvanes mrvanes linked a pull request Jan 15, 2024 that will close this issue
Make people status independent of CO status #129
Merged
@mrvanes mrvanes moved this from Todo to To be tested in SRAM development Jan 15, 2024
@baszoetekouw baszoetekouw modified the milestones: v30, v32, v31 Jan 16, 2024
@baszoetekouw
Copy link
Member Author

Dit werkt nog niet op test. Als een CO expired is, worden alleen alle gebruikers expired, en niet de CO (of de @All-Group) zelf.

@baszoetekouw baszoetekouw reopened this Feb 9, 2024
@github-project-automation github-project-automation bot moved this from To be tested to New in SRAM development Feb 9, 2024
@baszoetekouw baszoetekouw moved this from New to Todo in SRAM development Feb 9, 2024
@baszoetekouw baszoetekouw removed their assignment Feb 9, 2024
@baszoetekouw
Copy link
Member Author

Het helpt als je de goede versie deployt....
Werkt dus gewoon.

@baszoetekouw baszoetekouw moved this from Todo to To be deployed in SRAM development Feb 9, 2024
@sram-project-automation sram-project-automation bot moved this from To be deployed to To be tested in SRAM development Feb 9, 2024
@baszoetekouw baszoetekouw moved this from To be tested to To be deployed in SRAM development Feb 9, 2024
@sram-deploy-tools-automation sram-deploy-tools-automation bot moved this from To be deployed to Done in SRAM development Feb 27, 2024
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
SRAM development
Archived in project
Milestone
v31
Development

Successfully merging a pull request may close this issue.

Make people status independent of CO status SURFscz/plsc
2 participants
@baszoetekouw @mrvanes