[OPENAM-4459] OpenID Connect attribute mappings should be localizable Created: 09/Sep/14 Updated: 15/Dec/15 Resolved: 22/Dec/14
|Reporter:||Jelle Verbraak [X] (Inactive)||Assignee:||James Phillpotts|
|Labels:||12.0.0-Backlog, AME, TESLA, release-notes|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Sprint:||Sprint 76 - Team Tesla|
The attribute mapping for OpenID connect are currently being hard coded in the ScopeImpl.java class
scopeToUserUserProfileAttributes = new HashMap<String, Object>();
Map<String, Object> profileSet = new HashMap<String, Object>();
It would be nice that we have a OpenID attribute to local attribute mapper configuration field in the OpenID connect service (OpenAM console).
Note you need to configure your scopes in the oauth 2.0 client agent profile according to the claim names instead of the local attribute names (I don't find these steps in the documentation ).
Maybe you can make a section in the documentation about this topic.
|Comment by Jelle Verbraak [X] (Inactive) [ 09/Sep/14 ]|
Typo fixed in Description.
|Comment by Jonathan Scudder [ 22/Oct/14 ]|
@Sam: Consider this issue with Phill
|Comment by Sam Drew [ 23/Oct/14 ]|
This is currently implemented as a plugin point, rather than providing console based configuration options. It would be worth evaluating whether this needs to be a plugin, whether it should be configurable via the console, or some combination of the two.
|Comment by James Phillpotts [ 22/Dec/14 ]|
The oauth 2 provider now has configuration options for attribute mappings for the userinfo service.