Difference between revisions of "File:Imdi handshake.png"

From PDP/Grid Wiki
Jump to navigationJump to search
 
Line 1: Line 1:
 
Method used by the IMDI browser to obtain a certificate:
 
Method used by the IMDI browser to obtain a certificate:
  
# User click/chooses initialization option
+
# The user goes to a login/initialize function of the IMDI browser (this instructs the tool to create a private-/public keypair and a certificate signing request (CSR)) and...
# java browser starts a webbrowser
+
# ...lets the IMDI browser start a web browser...
# which points to the online CA at SURFnet
+
# ...to the SLCS with a hash of the CSR added
# Online CA redirects webbrowser to Identity Provider chosen by user
+
# The user gets redirected (optionally via a Where Are You From (WAYF)) to an Identity Provider (IdP) for his own institution.
# User logs in
+
# The user logs in at his IdP.
# webbrowser redirects back to online CA. Webbrowser can now be closed
+
# The web browser gets redirected back to the SLCS by the IdP, which informs the user he should go back to his application.
# After confirmation java browser now connects itself to online CA
+
# The user now has to instruct the IMDI browser that he is ready, which triggers the IMDI browser to send the full CSR to the SLCS.
# java browser retrieves certificate from online CA
+
# This step is transparent for the user: the Online CA signs a new certificate with the eduPersonPrincipalName as subject and SLCS sends it back. The IMDI browser stores this certificate and will be using it together with the private key it has, for client side authentication when setting up new https connections.

Latest revision as of 15:51, 5 January 2010

Method used by the IMDI browser to obtain a certificate:

  1. The user goes to a login/initialize function of the IMDI browser (this instructs the tool to create a private-/public keypair and a certificate signing request (CSR)) and...
  2. ...lets the IMDI browser start a web browser...
  3. ...to the SLCS with a hash of the CSR added
  4. The user gets redirected (optionally via a Where Are You From (WAYF)) to an Identity Provider (IdP) for his own institution.
  5. The user logs in at his IdP.
  6. The web browser gets redirected back to the SLCS by the IdP, which informs the user he should go back to his application.
  7. The user now has to instruct the IMDI browser that he is ready, which triggers the IMDI browser to send the full CSR to the SLCS.
  8. This step is transparent for the user: the Online CA signs a new certificate with the eduPersonPrincipalName as subject and SLCS sends it back. The IMDI browser stores this certificate and will be using it together with the private key it has, for client side authentication when setting up new https connections.

File history

Click on a date/time to view the file as it appeared at that time.

Date/TimeThumbnailDimensionsUserComment
current21:03, 13 October 2009Thumbnail for version as of 21:03, 13 October 2009811 × 276 (37 KB)Msalle@nikhef.nl (talk | contribs)Imdi handshake
17:21, 2 October 2009Thumbnail for version as of 17:21, 2 October 2009812 × 277 (31 KB)Msalle@nikhef.nl (talk | contribs)Reverted to earlier revision
17:20, 2 October 2009Thumbnail for version as of 17:20, 2 October 2009812 × 277 (31 KB)Msalle@nikhef.nl (talk | contribs)Reverted to earlier revision
17:20, 2 October 2009Thumbnail for version as of 17:20, 2 October 20091,052 × 744 (110 KB)Msalle@nikhef.nl (talk | contribs)Reverted to earlier revision
17:19, 2 October 2009Thumbnail for version as of 17:19, 2 October 2009812 × 277 (31 KB)Msalle@nikhef.nl (talk | contribs)better version
17:14, 2 October 2009Thumbnail for version as of 17:14, 2 October 20091,052 × 744 (110 KB)Msalle@nikhef.nl (talk | contribs)png version of imdi browser handshake

The following page uses this file: