User Tools

Site Tools


integration:start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
integration:start [2018/06/13 10:30]
tjotov [How it works]
integration:start [2018/06/14 12:11]
tjotov [Overview]
Line 1: Line 1:
 ====== No-code integration ====== ====== No-code integration ======
 ===== Overview ===== ===== Overview =====
-ADUCID offers No—code integration as default authentication method. It is implemented a set of modules including Apache web server and ADUCID core components. As result, target application receives user login name in http header (e.g. REMOTE_USER).+ADUCID offers No—code integration as default integration method. It is implemented a set of modules including Apache web server and ADUCID core components. As result, target application receives user login name in http header (e.g. REMOTE_USER).
 Many applications support header authentication by default or have authentication module available or can be easily modified to user header authentication. Many applications support header authentication by default or have authentication module available or can be easily modified to user header authentication.
  
Line 9: Line 9:
 ===== How it works ===== ===== How it works =====
   - User opens a web application   - User opens a web application
-  - Apache resolves it 401 - unauthenticated+  - Apache resolves it with code 401 - unauthenticated
   - [[integration:binder|ADUCID Binder]] page is diplayed - it is ADUCID authentication page with login button and QR code   - [[integration:binder|ADUCID Binder]] page is diplayed - it is ADUCID authentication page with login button and QR code
   - As soon as user authenticates page is reloaded and proxypass used to retrieve the back-end application for user   - As soon as user authenticates page is reloaded and proxypass used to retrieve the back-end application for user