-
Notifications
You must be signed in to change notification settings - Fork 0
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
Move to different identifier for Services in PLSC #117
Milestone
Comments
FlorisFokkinga
changed the title
Move to different identifier for Services (
Move to different identifier for Services
Nov 17, 2023
FlorisFokkinga
changed the title
Move to different identifier for Services
Move to different identifier for Services in PLSC
Nov 17, 2023
Fixed in 8d26d71 |
Works; only now it's very hard to distinguish different orgs. Please add |
Fixed in faadd9f but /api/plsc/sync does not contain service[short_name] so assigned entity_id for now. |
Merged
sram-deploy-tools-automation
bot
moved this from To be deployed
to Done
in SRAM development
Dec 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, services are identified by their entity_id in the ldap tree. The DNs look like
dc=http://test.beta.sram.surf.nl/test1,dc=services,dc=sram,dc=surf,dc=nl
for example.This is annoying for two reasons:
Therefore, SBS will introduce a new
ldap_identifier
attribute for services (see SURFscz/SBS#1054). plsc should use this instead of the entity_id to build Service trees.The text was updated successfully, but these errors were encountered: