[OPENAM-5786] Creating an UMA resource in the AS sends an error message
Created: 08/Apr/15 Updated: 22/Apr/15 Resolved: 10/Apr/15
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
OpenAM
UMA, XUI
13.0.0
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Environment:
Bug
Victor Ake
Fixed
AME, TESLA
Not Specified
Issue Links:
Relates
relates to
QA Assignee:
Sprint:
13.0.0
Priority:
Assignee:
Votes:
Major
James Phillpotts
0
Not Specified
Not Specified
OpenAM 13.0 Build 13252
Embedded Conf store and User, and everything
OPENAM-5805
Sharing resources fails
Resolved
Alex Walker
Sprint 83 - Team Tesla
Description
When creating a resource set in OpenAM using the REST interface, an error message is received from time to tim
the time, it sometimes works when one "updates" the Policy Agent Config, i.e. a simple save can do it) instead o
resource set id of the resource just created.
1. Get a PAT
$ curl --request POST --header "Content-Type: application/x-www-form-urlencoded" --data
"client_id=RSClient&client_secret=cangetin&grant_type=password&scope=uma_protection&username=alice&
http://as.uma.com:8080/openam/oauth2/access_token
{"scope":"uma_protection","expires_in":299,"token_type":"Bearer","refresh_token" ;:"05478ce6-55a0-4646-a06
3d1709aa162c","access_token":"38b470e6-28a0-48ad-8941-d5f580b58aca"}
2. Add a resource set
$ curl --request POST --header "Authorization: Bearer 38b470e6-28a0-48ad-8941-d5f580b58aca" -d '
{ "name": "example2", "scopes": [ "http://rs.uma.com:9001/data/scopes/view"; ], "type": "http://rs.uma.com:900
' http://as.uma.com:8080/openam/oauth2/resource_set
3. Instead of receiving this:
{"_id":"5d968665-7e77-4eed-baab81860dcb85fc18","user_access_policy_uri":"http://as.uma.com:8080/openam/XUI/#uma/share/5d968665-7e7781860dcb85fc18";}
Almost always, one gets:
{"error":"server_error","error_description":null}
A restart of the OpenAM, and sometimes re-saving the OAuth2/OIDC Client can fix it, but it is most of the time
error.
Comments
Comment by James Phillpotts [ 10/Apr/15 ]
Changes in the policy engine caused this. This issue is fixed, but there is another issue
uncovered where the policy engine's ResourceType now restricts the action values that can be
used, which in UMA are not known up front. Raised for this.
Comment by Alex Walker [ 22/Apr/15 ]
Verified fix in OpenAM 13.0.0-SNAPSHOT Build 13537 (2015-April-22 02:55)
Generated at Tue Feb 09 16:33:03 GMT 2016 using JIRA 6.3.9#6339sha1:46fa26140bf81c66e10e6f784903d4bfb1a521ae.