Versions Compared

Old Version 6

changes.mady.by.user Unknown User (schofield)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (peter.schober@univie.ac.at)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Clients (humans) are happy when Google stores an additional password to provide the service.
    1. Users are "educated" to put their password everywhere!!!
    2. Helpdesks try to educate users to avoid phishing attacks.
  2. Applications don't support SAML/SASL or SAML-ECP.
  3. OAuth is a better model than long term replayable key.
  4. Constrained by the install base.
  5. Long term solutions will emerge and be deployed (Moonshot).
  6. Clients (IdPs)  want a scalable solution.
  7. As an alternative to storing passwords in O365:
    1. password' provided to user + O365 talks to proxy which uses alternative UserDB.
    2. user talks to IMAP proxy + proxy verifies auth to Home UserDB + proxies IMAP to O365.
    3. currently a PoC with TUDelft.
  8. Need to do the same with Google Apps.
  9. Offering these interim solutions might halt providers solving the problem correctly.

ACTIVITIES GOING FORWARD / NEXT STEPS

  1. Engage the enterprise space to encourage Microsoft.
  2. Develop a Proof of Concept proxy on top of simpleSAMLphp which supports XMPP, IMAP, SIP to encourage commercial solutions providers to adopt...

RESOURCES

If slides, websites or other pointers for information are used in the session, please attach them to this page or send them to the secretary for posting.

...