[mitreid-connect] mitreid-connect IDP: support additional authentication schemas.

[Justin Richer]

No, this won't work and isn't using OAuth properly. You don't want the client app to intercept the credentials, you can have the server accept them directly. We've deployed the server using Kerberos authentication, but the client and rp never see the Kerberos tickets. 
--Justin
 Sent from my phone
-------- Original message --------From: Michael Furman <michael_furman at hotmail.com> Date: 9/1/16  4:46 PM  (GMT+02:00) To: mitreid-connect at mit.edu Subject: [mitreid-connect] mitreid-connect IDP: support additional	authentication schemas. 




Hi all,
I want to extend mitreid-connect IDP and to support additional authentication schemas, like Basic Authentication (or Kerberos).
I read the following document:
https://github.com/mitreid-connect/OpenID-Connect-Java-Spring-Server/wiki/Server-configuration


In the current version we have RestAPI clients that accesses our application with Basic Authentication.




I just want to ensure the following flow will work when we will start to use OpenID-Connect.





1)     
A RestAPI client accesses RP (our application) with the Basic Authentication header

2)     
RP redirects the request to mitreid-connect IDP using OpenID-Connect protocol

3)     
The modified mitreid-connect IDP authenticates the request using the Basic Authentication header.

4)     
mitreid-connect IDP redirects request back using OpenID-Connect protocol

5)     
RP (our application) authenticates the request using OpenID-Connect protocol
Also, I hope the same flow will work for other authentication schemas (e.g. Kerberos).
Thank you in advance for your help.
Best regards,
   Michael





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/mitreid-connect/attachments/20160901/dcb27cb8/attachment-0001.html