Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.php > #17123

Re: Seamless SSO

From Tim Ritberg <tim@server.invalid>
Newsgroups comp.lang.php
Subject Re: Seamless SSO
Date 2016-10-07 09:50 +0200
Organization TOTA
Message-ID <nt7k4s$j0a$1@tota-refugium.de> (permalink)
References (5 earlier) <nt3b58$l66$1@jstuckle.eternal-september.org> <nt3cna$tlt$1@tota-refugium.de> <nt3h5t$der$1@jstuckle.eternal-september.org> <nt3i22$1ue$1@tota-refugium.de> <nt3nva$6ff$1@jstuckle.eternal-september.org>

Show all headers | View raw

Am 05.10.2016 um 22:31 schrieb Jerry Stuckle:
> Again - why should PHP control the login process?  SSO is normally
> handled by the server - which is why you don't get a plain-text password
> (security exposure).'
> 
> Fallback would be a form, as Arno indicated.
> 

How to design a fallback scenario with an Apache Auth Module?
Those modules give back 403.

Tim

Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-02 11:37 +0200
  Re: Seamless SSO "Peter H. Coffin" <hellsop@ninehells.com> - 2016-10-04 12:44 -0500
    Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-04 20:12 +0200
  Re: Seamless SSO Arno Welzel <usenet@arnowelzel.de> - 2016-10-04 20:19 +0200
    Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-04 20:55 +0200
      Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-04 20:47 -0400
        Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-05 09:52 +0200
          Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-05 12:53 -0400
            Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-05 19:19 +0200
              Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-05 14:35 -0400
                Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-05 20:50 +0200
                Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-05 16:31 -0400
                Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-07 09:50 +0200
                Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-07 10:48 -0400
                Re: Seamless SSO Arno Welzel <usenet@arnowelzel.de> - 2016-10-07 17:44 +0200
                Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-07 18:04 +0200
                Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-07 17:12 -0400
                Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-24 12:33 +0200
                Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-24 08:22 -0400
                Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-24 15:51 +0200
                Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-24 10:55 -0400
      Re: Seamless SSO Arno Welzel <usenet@arnowelzel.de> - 2016-10-07 17:47 +0200
        Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-07 18:07 +0200
          Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-07 17:13 -0400
            Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-08 00:50 +0200
              Re: Seamless SSO Jerry Stuckle <jstucklex@attglobal.net> - 2016-10-07 19:42 -0400
              Re: Seamless SSO Arno Welzel <usenet@arnowelzel.de> - 2016-10-08 12:33 +0200
          Re: Seamless SSO Arno Welzel <usenet@arnowelzel.de> - 2016-10-08 12:31 +0200
            Re: Seamless SSO Tim Ritberg <tim@server.invalid> - 2016-10-08 13:19 +0200

csiph-web