Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

More details on how VIVO will integrate with a Single Sign-On system like Shibboleth or CUWebAuth.

What is the mechanism?

  • The common way:
    • sit behind a reverse proxy
    • proxy intercepts a special request
    • after login is complete, proxy redirects to the original request.
    • HTTP header must contain a UID or equivalent identifier.
    • Commonly Apache, with a module to accomplish the work
  • The other way
    • specify a redirection URL
    • No proxy or interception required.
    • HTTP header is the same.
  • Where is the /loginExternalAuthReturn page?
    • VIVO just redirects from there.
      • Home page
      • Profile page
      • New account

How to debug?

  • Is the request being intercepted?
    • Increase the log settings
    • Look at headers
    • Is your UID in a header?
    • Configure VIVO to read that header.
  • Otherwise, configure the reverse proxy to intercept it.

 

  • No labels