On 5/18/2015 12:23 PM, Richard Hipp wrote:
On 5/18/15, Ross Berteig wrote:
On 5/15/2015 7:03 PM, Richard Hipp wrote:
Imagine a user Hortense who in the course of history, had access to A
and B, but before I realized that there should be a login group at all.
So she has accounts in both repos,
On 5/18/15, Ross Berteig wrote:
> On 5/15/2015 7:03 PM, Richard Hipp wrote:
>
> Imagine a user Hortense who in the course of history, had access to A
> and B, but before I realized that there should be a login group at all.
> So she has accounts in both repos, and likely has different passwords in
On 5/15/2015 7:03 PM, Richard Hipp wrote:
The login-group feature gives you single sign-in.
Suppose you have multiple customers, some of whom have access to A and
others B and other C and some to combinations of these three:
Alice: A
Bob: B
Cindy: C
David: A and B
Elly: B and C
Fred:
On 5/15/15, Ross Berteig wrote:
>
> The bottom line is that aside from the Admin / Login-Group page showing
> for both A and B that they know each other's file names, and the Admin /
> Users / SomeUser page offering the radio button for change local vs. the
> whole group, I'm not seeing any benefi
I think you have to login to A.fossil to obtain a (shared) session cookie.
After that your users should be able to access B.fossil with out loging in
to B.fossil
On Friday, May 15, 2015, Ross Berteig wrote:
> I use fossil a lot internally. I've meant to try the login-group feature
> since it wa
I use fossil a lot internally. I've meant to try the login-group feature
since it was released, but never had a pressing need. Until yesterday.
And now I am confused.
I have two repositories for projects for the same customer, and it would
be convenient to use the same credentials in both. Whi
6 matches
Mail list logo
