Thank you, @ilgrosso!
--
View this message in context:
http://syncope-user.1051894.n5.nabble.com/Login-Logic-tp5709081p5709083.html
Sent from the syncope-user mailing list archive at Nabble.com.
While registering the new user, I'd like to be able to save additional data.
In the default installation, there was a 'plainAttrs' schema entry for
'email', which I replaced by lastname and firstname, both defined as String
types, not required, no validation, no integrity checks.
When I try to
I hope I am not getting on the wrong track... But here goes. Now that I've
worked out the logic for Self-Registration, I am wondering If and How I
could manage the login process via Syncope.
I have not found any REST methods for "authenticating" the user. That is,
sending in a combination of
ilgrosso wrote
> short answer: from Admin Console, go to Configuration > Types >
> AnyTypesClasses, edit 'BaseUser' and add 'firstname' and 'lastname' there.
Thanks! That worked like a charm!
ilgrosso wrote
> Long answer: invest some time in understanding how the type management
> works in
First of all, THANK YOU, Francesco, for a fast reply!
ilgrosso wrote
>
> vladz wrote
>> 1. (POST /users/self) When I execute it from the browser, I invariably
>> receive CODE 403 with message "Access to the specified resource has been
>> forbidden.&q
HA! It looks like the issue with "curl" not going through was that I used
the suggested by SwaggerUI line, and it contained 2 errors:
1. (This one I fixed initially, so adding it here for completeness.) The
"@class" attribute is shown there HTML-escaped as "%40class", which when
sent via curl
