Hi Aymen
re issue with passing the claims containing "/", in your example below,
something like
'http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname'
needs to have "/" %-encoded for the the server to understand it
represents a single value as opposed to a sequence of "/" separated path
segments.
It may be simpler to have such properties to pass as query parameters.
If it is passed as a path segment value the browser will unlikely encode
"/" because "/" is a valid path separator. if you do from some script
then do encode it first
HTH, Sergey
On 21/08/16 21:56, Aymen Furter wrote:
Hi there!
A little update regarding the Fediz IDP UI I am currently building:
- Integrated into Maven Build Process
See my fork: https://github.com/aymenfurter/cxf-fediz
(However, this creates a dependency. The Build Server needs to have npm
installed. Is this an issue?)
- An error message is displayed when a server error occurs.
- Lists do now get updated consistently.
- Login now works correctly (However, it's still Basic Auth based)
- I currently face an issue when accessing objects using the REST Api that have
"/" in them.
(e.g.
http://idp.aymenfurter.ch:8040/services/rs/claims/http://schemas.xmlsoap.org/ws/2005/05/identity/claims/givenname)
Maybe an issue regarding my Tomcat Setup? If someone has input regarding this
I would be very thankful!
- Testinstance is running here: http://idp.aymenfurter.ch:8040/admin/index.html
(default credentials)
best regards
Aymen
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
