We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

What is the intended functionality of the "user" property introduced in 21C?

Received Response
24
Views
1
Comments

This post was created as part of a How to Service Request (SR)

Release: 21C

Summary of the question: What is the intended functionality / Implementation of the feature listed in 21C release notes? It's not clear how this can be implemented/utilized but according to the release notes, there is no configuration needed in CPQ to enable this. This doesn't seem correct as there is an implied need for an uploaded public cert or private key.

My understanding is that Admins should be able to customize the token passed to CPQ from an eCommerce app or perhaps an IDP to implement some version of an SSO with quick registration users. This seems to be in conflict with configuration options in admin > partner orgs as I cannot set "enabled for SSO" to "yes" for the quick registration type org. 

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!