> I hope I am not getting on the wrong track... But here goes. Now that
> 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
> sending in a combination of user name and password, receiving back an
> identity key or user object.
> How can the client app resolve the user stored in syncope via
> self-registration where the app itself does not keep a separate user
Up to Syncope 2.0.2 (e.g. the current stable version), the only
authentication method supported (at least, by default) is the HTTP Basic
Authentication: this means that each and every REST method invocation
requires an 'Authentication' HTTP header to be sent.
On the Syncope Core, such Authentication header is processed by the
Spring Security components, which verify the passed credentials against
the internal storage.
Starting with Syncope 2.0.3, however, the authentication process is
reviewed, and support for JSON Web Tokens is introduced: the new process
is described at . Syncope 2.0.3 is expected to be release in some
time - say about one month from now.
FYI, the current REST features are described in .