You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer, I want the existing Education API implementation to be revived and run as a separate service so that it can be maintained and scaled independently.
Description
The current Education API implementation should be reactivated and deployed as its own standalone service. This separation improves maintainability, allows independent scaling, and prepares the service for future extensions.
Acceptance Criteria
Existing Education API implementation is restored and functional
Education API runs as a separate service
Documentation updated on how to run and access the service
Create docker compose ( OC DEV Tools )
Information Details
here are information about API and provisioning etc.
In order to make the API easier to understand we should probably make a few attributes optional that only have a meaning in the School Context:
Schools/Tenants: We likely won't need the schoolNumber attribute, which in our current implemenation is required . In MS Graph itself it optional.
EducationUsers:
The primaryRole attribute is currently required, we don't need that for the MultiTenant use case.
The identities attribute is supposed to contain the sub and issuer claim of the user. We/The provider might not even know those when users are provisioned. Those should be optional as well. (At least when an externalId (User Lookup by External ID #1599) is set in the request)
Userstory
As a developer, I want the existing Education API implementation to be revived and run as a separate service so that it can be maintained and scaled independently.
Description
The current Education API implementation should be reactivated and deployed as its own standalone service. This separation improves maintainability, allows independent scaling, and prepares the service for future extensions.
Acceptance Criteria
Information Details
here are information about API and provisioning etc.
https://github.com/opencloud-eu/opencloud/blob/main/docs/adr/0002-use-education-api-for-multitenant-user-provisioning.md
In order to make the API easier to understand we should probably make a few attributes optional that only have a meaning in the School Context:
schoolNumberattribute, which in our current implemenation isrequired. In MS Graph itself it optional.primaryRoleattribute is currently required, we don't need that for the MultiTenant use case.identitiesattribute is supposed to contain thesubandissuerclaim of the user. We/The provider might not even know those when users are provisioned. Those should be optional as well. (At least when anexternalId(User Lookup by External ID #1599) is set in the request)