Brend-Smits
commented
3 years ago After discussing this with our stakeholders, we decided to not work on this issue at this moment. The time spent on getting everything in order with governance is not currently worth the investment, seeing as I'm already short on time.
Our technical implementation is ready to plug-in the client id/secrets from Surf. The only thing we need to take care of is migrating to a Fontys approved hosting environment like Azure. Fontys has contracts with certain third parties that are required by parties like Surf. Which host we should switch to is investigated in #250.
When the platform reaches the point where it's stable enough and feature-rich to move out of beta, we can look into adding Surf. This does not mean that we will no longer design the platform with other universities and schools in mind, this is still our focus.
I will be closing this issue for now seeing as we don't have plans for this in the upcoming sprints.
Is your feature request related to a problem? Please describe. We want Digital Excellence to grow beyond just Fontys. Other universities currently are unable to login and interact with the platform.
Describe the solution you'd like Set up talks with Fontys II&A to discuss our ambitions and to see what we can do right now to implement SurfConext. We contacted them earlier and according to Marcel, integration with Surf is possible using the FHICT API. It's currently connected to 4 universities/schools. We have to discuss with our stakeholders if we want to settle with this, if we can expand it to more universities, and what is needed from our side for this. I expect implementation to be rather seamless as long as appropriate standards are being used by FHICT and Surf, we should just be able to add the client to our IdentityServer and add a button on the Frontend.
Steps to take: