[midPoint] REST authentication

[Petr Gašparík - AMI Praha a.s.]

Hi,
REST API does not work with browser, so what is the concept of "SSO" here?

We did SSO in past, with HTTP header and with CAS, in core concept it
requires user's browser. If you use REST, you use midPiont in API mode.
There is no SSO AFAIK. You submit user/password every time, as REST is
stateless.

cheers, P.

--

s pozdravem

Petr Gašparík
solution architect

gsm: [+420] 603 523 860
e-mail: petr.gasparik at ami.cz


AMI Praha a.s.
Pláničkova 11
162 00 Praha 6
tel.: [+420] 274 783 239
web: www.ami.cz


[image: AMI Praha a.s.]

[image: AMI Praha a.s.]
<http://www.ami.cz/reseni-a-sluzby/bezpecnost-dat/audit-roli-a-opravneni-sap>

Textem tohoto e-mailu podepisující neslibuje uzavřít ani neuzavírá za
společnost AMI Praha a.s.
jakoukoliv smlouvu. Každá smlouva, pokud bude uzavřena, musí mít výhradně
písemnou formu.


2016-12-08 9:25 GMT+01:00 Pertti Kellomäki <pertti.kellomaki at datactica.fi>:

> Hi,
>
> The SSO Howto https://wiki.evolveum.com/display/midPoint/MidPoint+and+SSO+
> HOWTO states that "midPoint can be configured to accept the
> "authentication" based solely on the presence of the username in the HTTP
> header."
>
> Is it possible to configure the REST api to do the same? I am looking at
> how to do authentication for REST clients that use an external SSO.
>
> Pertti
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20161208/59d17a6e/attachment.htm>