Michael,

The way it worked was that the auth module would look for a token. If it didn't 
exist the user would be redirected to our SSO login page (not A4D, hosted 
elsewhere). 
Once the logged in, the token was visible, the user was allowed access to our 
A4D site and we could identify them based on information in the request 
headers. There was either a username or person_id that we could use to lookup 
details via LDAP. 
If I recall we would pack the details into the A4D Session once they had access.

It has been a few years since we had to abandon it because the auth module was 
no longer supported. Jasig CAS is/was an open source project and their Mac 
support was very limited. I no longer have access to a version of the A4D code 
that implemented SSO or I'd pass it on.

Hope that helps,

Brad

On 4/25/18, 9:28 AM, "Active4D-dev on behalf of Michael Check" 
<active4d-dev-boun...@aparajitaworld.com on behalf of michaelr.ch...@gmail.com> 
wrote:

    Thanks Brad.
    
    Can you explain further how A4D then serves pages with user data after the
    Apache Auth module interaction?
    User Auth in Jasig --> Apache Auth --> A4D ?
    If that is the case, how do (did) you pass along user data to A4D?
    
    Our client is running a SitePoint system that would, I think, pass along
    the user and token data to our Windows system running Apache --> A4D (on
    the same box). I'm just unclear on how we unpack the authenticated user
    data in A4D - or if that is even available from within A4D without first
    querying or placing it somewhere retrievable by A4D.
    
    Thanks,
    
    Michael Check
    
    On Mon, Apr 23, 2018 at 10:07 AM, Perkins, Bradley D <bperk...@lanl.gov>
    wrote:
    
    > Michael,
    >
    > When we did this in the past we did so by using an Apache  auth module
    > that was compatible with the SSO solution we used (Jasig CAS). It worked
    > for us because we had A4D behind Apache. We had to remove it when a Mac OS
    > major version update broke that module and replaced it with LDAP based
    > authentication (The SSO solution uses the same credentials).  There might
    > be an Apache (or Nginx) module for your SSO solution.
    >
    > Hope that helps,
    >
    > Brad Perkins
    >
    > On 4/23/18, 8:46 AM, "Active4D-dev on behalf of Michael Check" <
    > active4d-dev-boun...@aparajitaworld.com on behalf of
    > michaelr.ch...@gmail.com> wrote:
    >
    >     Hi all, long time no talk (I miss it here),
    >
    >     Wondering if any of you have implemented a SAML or other Single Sign 
On
    >     (SSO) solution with A4D?
    >
    >     I have a client looking for an implementation direction for SSO and
    > they're
    >     suggesting SAML with a small A4D app.
    >
    >     Thanks!
    >
    >     Michael Check
    >     _______________________________________________
    >     Active4D-dev mailing list
    >     Active4D-dev@aparajitaworld.com
    >     http://list.aparajitaworld.com/listinfo/active4d-dev
    >     Archives: http://active4d-nabble.aparajitaworld.com/
    >
    > _______________________________________________
    > Active4D-dev mailing list
    > Active4D-dev@aparajitaworld.com
    > http://list.aparajitaworld.com/listinfo/active4d-dev
    > Archives: http://active4d-nabble.aparajitaworld.com/
    _______________________________________________
    Active4D-dev mailing list
    Active4D-dev@aparajitaworld.com
    http://list.aparajitaworld.com/listinfo/active4d-dev
    Archives: http://active4d-nabble.aparajitaworld.com/

_______________________________________________
Active4D-dev mailing list
Active4D-dev@aparajitaworld.com
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://active4d-nabble.aparajitaworld.com/

Reply via email to