[Xerte-dev] Re: Using Two Authentication Methods

[Tom Reijnders]

- Static will never be upgrade friendly, or we need to do some serious 
work on the installer.

Three options I see.

1. Add the 1 user to ldap, but I am sure you considered that already. 
(upgrade safe)
2. Add static accounts to the Ldap method (NOT upgrade safe)
3. Make two authentication methods possible, and use Db for the 
'static'user, but this requires the most work, I don't know if it can be 
done, but this one is also upgrade safe.

Tom

Op 16-5-2013 15:28, Julian Tenney schreef:
>
> Hi,
>
> I need a bit of help from someone who knows the authentication stuff 
> better than me:
>
> We have some cases where, in the past, we've kept a few usernames / 
> passwords in the auth code, and have checked against those before 
> checking against LDAP. There are some collective efforts here where 
> content is passed to a central admin account -- one that has static 
> authentication. Lots of people create content in their own accounts, 
> and then pass it to the admin account when it is finished, and that 
> sets up a lot of content for feeds, etc. Downstream, a website reads 
> the folder feeds and displays the content.
>
> When we upgraded, we lost this capability. Now that user can't login.
>
> So I need to be able to either hardcode a username / password in 
> somewhere (I know, I don't like it either) or have two auth methods, 
> static, and then LDAP (or the other way around) if the first one 
> fails, and I need a solution that won't break in the future when we 
> upgrade again, because this is a real pain.
>
> What's the best solution?
>
> Thanks,
>
> Julian
>
>
>
>
>
>
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev

-- 
--

Tom Reijnders
TOR Informatica
Chopinlaan 27
5242HM Rosmalen
Tel: 073 5226191
Fax: 073 5226196

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20130516/ca292292/attachment.html>