Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fairkom fairkom
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • fairlogin
  • fairkomfairkom
  • Issues
  • #2

Closed
Open
Created Jun 21, 2017 by David Ayers@ayersMaintainer

Analyse and document how to handle cascaded authentication

Assuming that a web application like GroupOffice receives a login request an defers authentication to WSO2 to authenticate a user but does not itself have the password needed by the IMAP, how can GO authenticate its IMAP access?

Assuming that a web service like z-push receives an active sync request and defers to WSO2 to authenticate the user, will it use XOAUTH2 or some other mechanism to authenticate to IMAP storage?

Write a simple web application and a simple web service to simulate this type of access to test how WSO2 can be used for cascading service authentication.

Edited Jun 22, 2017 by David Ayers
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking

gitlab project and software management by fairkom.eu - more open source web apps at fairapps.net