On 05/04/2015 01:21 AM, Todd Morgan wrote:
Let me ask a different question then :-) (as CROWD and LDAP are both acceptable
options for me as they represent the same information - crowd is just easier to
setup and limit its scope).
Note: There is no evidence that Crowd is causing any problems and it
might be premature to switch to LDAP.
If I connect up an LDAP to authenticate against Kallithea what is the end user
experience for the following when the user only exists with LDAP:
- user trying to pull from an authenticated repo (ie one they already have from
an old system with the same URL)? Will it just pull the changes? What about a
push?
Yes.
- user hitting the main Kallithea URL for the first time?
-- will they have to register? Will they merely have to enter their old
credentials (from LDAP) and it will work?
Nothing special.
The LDAP information will be propagated to the database when the user
logs in.
But give LDAP a try ... and then try Crowd again before you make your
decision.
/Mads
_______________________________________________
kallithea-general mailing list
[email protected]
http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
