Hi all!

Ok, the short version of what I am needing to do is not require a separate login for OST when the customer already has an account and/or is logged in to our system.

The customer authentication is handled via a REST API on a remote server (non-local MySQL) - so this really makes any kind of LDAP setup difficult as far as I know.

So, how can I have a SSO w/o LDAP or AD...when OST doesn't have an API to support user management?

Things Im grasping at:

a) Create an OST user account (ajax post?) with the same email/pw as the customer account when the customer account is created. Then, set whatever OST session vars are needed when the customer logs in to our system.

b) Completely rewrite the OST authentication to make REST calls to our customer DB...and kill any potential for OST updates :/

Am I completely crazy here or is there some kind of option to do what I need?

Thanks for any help!

I've been looking at the PHP code regarding LDAP a lot and it seems they've made abstract Authentication Backend classes and the like. Looking at the existing plugins maybe the place to start at creating your own?

@[deleted] Thanks, but I was hoping for more of a quick and dirty hack instead of writing a plugin.As another example, Im trying to figure out the token system so I can just query the OST DB directly for tickets associated with the customer's email and display a list of tickets (URLs) using the query string token that's sent in the staff response emails.If I can pull that off, then we wont even have to worry about the OST user accounts.

Write a Reply...