Actually the sso integration in Developer Portal with RH SSO allows mapping just one user field "org_name".
A typical use case I've found in customers, they usually manage all their developers info into their corporate IdP, also they store there some authorization info, like for instance developer's department. In a specific example, according the developer's department content, the user will be able to subscribe a 3scale service or not through the Developer Portal.
We are asking for resolving the requirement explained in the use case before allowing mapping a 3scale user custom field with a RHSSO user atribute in the sso developer portal integration with RHSSO.