Alternatives setting up Federated Identity Provider

Question

When setting up federated identity provider there are three alternatives today, None, Microsoft Entra ID and AVEVA Connect. 
 Are there any plan to extend this list? or is it possible to add providers, like OAuth2 for example?

Ernst van Wyk · Accepted Answer

It is not currently planned. 
 To explain that a little bit: I am following an internal definition where planned items have target dates, resource and schedules assigned vs ideas which we are tracking but have not prioritised high enough to start planning yet. 
 We are planning to release a new version (System Platform 2026) towards the end of this year or early next year, but this item is not on that plan at the moment and I doubt that i'd be able to find something to drop from that plan to make space for this. 
 This item is however on our backlog, where there is a bunch of ideas that we constantly re-evaluate and stack rank based on the market's requiremetns, number of requests, strategic value etc. I will tell you that this is not the first time we are hearing the requirement but it is also not being asked for very frequently. 
 So here is my suggestion - We maintain an ideas portal where anyone can add ideas or vote on ideas that others had. This allows us to track the market requirement for the ideas and helps us prioritise ideas so it can be added to the plan. I have added Support OAuth as a federated identity provider to the portal and added a proxy vote on your behalf. If it attracts a lot of votes, we can move it up on the priority list. 
 To answer your questions more directly: Even if I were to find a feature on the current plan to drop, the earliest this will make it into the product is ~10 months from now. A more realistic estimate would be the release after System Platform 2026, which is probably only 18 to 24 months from now. 
 - Ernst

Alternatives setting up Federated Identity Provider

Top Replies