REST authentication and attributes

206 views
Skip to first unread message

bwh

unread,
Apr 6, 2017, 4:29:56 PM4/6/17
to CAS Community
Hey community,

at the moment I'm trying to setup my CAS installation with REST-Authentication (https://apereo.github.io/cas/5.0.x/installation/Rest-Authentication.html)

The authentication works fine so far.
As Response i get:

HTTP status 200

Content:

{
  "id": "max",
  "attributes": {
    "member": "some",
    "request": "tata",
    "foo": "baa"
  }
}


My Problem ist that the attributes are not set to the To the principal. I'm pretty sure i forgot some configuration. 
Can yomeone help me please.

Currently I'm using CAS version 5.0.4

Dmitriy Kopylenko

unread,
Apr 6, 2017, 4:51:58 PM4/6/17
to cas-...@apereo.org
Currently in both 5.0.x and master branches, the configuration for the REST authn handler “blindly" sets the person directory principal resolver, disregarding any attributes returned from the remote HTTP resource:



If the original intention was to be able to utilize any attributes returned from REST endpoints as authenticated principal attributes, we could consider this as a bug.

File an issue on Github: https://github.com/apereo/cas/issues

Cheers,
D.
--
- CAS gitter chatroom: https://gitter.im/apereo/cas
- CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html
- CAS documentation website: https://apereo.github.io/cas
- CAS project website: https://github.com/apereo/cas
---
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cas-user+u...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/86b821da-ceb0-4797-836f-2a3cabfdbe86%40apereo.org.
Reply all
Reply to author
Forward
0 new messages