On Jan 10, 2018, at 6:05 PM, Patrick Huang wrote:
Not only the password mismatch. The problem is username (among other
things, e.g. the identifier url, name and email, are returned from
openstackId authentication and can be changed by user then saved to Zanata)
has to be
Not only the password mismatch. The problem is username (among other
things, e.g. the identifier url, name and email, are returned from
openstackId authentication and can be changed by user then saved to Zanata)
has to be unique in Zanata. Since the identifier values come from two
different
>
> According to his comment, it would be nice if Zanata manages openid full
> url by separating
> into domain part (e.g., "openstackid.org") and rest part (e.g., "/...").
> @Patrick, would it be possible to support in Zanata
> as a new feature?
As much as I would like to solve issue asap, I
Hi Ian,
Not every openID provider returns the identifier URL in such pattern. In
fact it might not be URL at all (it just need to be unique to that
provider). So technically Zanata won't be able to support the feature you
proposed below.
I think fresh database will work well and easier to
Technically those affected users could just update their password on both the
OpenStackID production and dev sites. Then the problem would be solved. I can’t
imagine we are talking about that many people that have changed their passwords?
Thanks,
Jimmy McArthur
Hello,
I would like to update this (sorry for my late sharing on this mailing
list and infra team):
- Jimmy commented on the Etherpad on Dec 13.
According to his comment, it would be nice if Zanata manages openid full
url by separating
into domain part (e.g., "openstackid.org") and rest
I've put my comments in the etherpad.
On Wed, Dec 6, 2017 at 11:19 AM, Ian Y. Choi wrote:
> Hello,
>
> Since Zanata upgrade to 4.3.1 on translate-dev.openstack.org is going
> well [1],
> I think it is a good time to discuss translate-dev.o.o authentication
> problems.
>
> I
Hello,
Since Zanata upgrade to 4.3.1 on translate-dev.openstack.org is going
well [1],
I think it is a good time to discuss translate-dev.o.o authentication
problems.
I wrote a brief current problem on authentication issues in
translate-dev.o.o and my suggestion on proposed solution
: