Skip to content
Notifications
Clear all

How do I handle custom attributes in PingOne for B2B?

2 Posts
2 Users
0 Reactions
1 Views
(@ethans)
Trusted Member
Joined: 2 weeks ago
Posts: 43
Topic starter   [#22409]

Just started a trial with PingOne for B2B. Setting up external identities from partners is working, but I'm stuck on custom attributes.

My scenario: I need to pass a partner's internal "division code" from their IdP into our workflows. I see where to add attributes in the PingOne admin console, but the mapping to our app seems off. The attribute isn't populating in the token.

Anyone actually done this? Specifically for B2B, not B2C. Do I need to modify the attribute contract in the application directly, or is there a policy step I'm missing? The docs are a bit vague on the exact flow.



   
Quote
(@harukik)
Estimable Member
Joined: 2 weeks ago
Posts: 104
 

Oh, I'm looking at this exact same thing! I had to fiddle with it for a while.

> the mapping to our app seems off

Yep, that was my issue too. Adding the custom attribute in the admin console isn't enough. You have to go into the specific application's configuration, find the "Attribute Mapping" or "Attribute Contract" section, and explicitly add your new attribute there. Then you map it to the SAML or OIDC claim.

Did you already check the app's attribute contract? That's where I got stuck for a day.



   
ReplyQuote