1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
Industry: MFP
My Role: Project Manager, Development Leader
Stakeholders: IT dep, Product Development dep
2. What product and version are you currently running?
RV&S 13.0.0.1
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
Our customer used to use LDAP and AD(Active Directory) as a authentication system.
However, they are moving toward more generic technique that can be used on multiple platforms,
such as Web-based, mobile, rich clients and JavaScript clients.
In Fact , the customer will soon stop supporting LDAP and AD(Active Directory) and instead they are now
supporting only Open ID connect and SAML.
We understand SAML is an authentication system mainly for Web UI.
But for Open ID connect, it allows clients of all types, including Web-based, mobile, and JavaScript clients
to request and receive information about authenticated sessions and end-users.
We would like to request PTC to support Open ID connect on RV&S Rich client.
4. What is the use case for your organization?
End users should be able to login to RV&S rich client with their central-maintained ID and password.
The central maintained ID and passwords exists in LDAP Directory Service. However, the authentication
should be done via Open ID connect or SAML. Since Open ID connect covers clients of all type,
we are asking for Open ID connect support.
5. What business value would your suggestion represent for your organization?
We are now using LDAP authentication. However, our customer's LDAP authentication support will
end on March 2023. After that, there will be no way left to realize RV&S login using central-maintained ID and password.
As for security reasons, it is a must requirement to realize RV&S login using central-maintained ID.
