I win my internal bet: I was sure it would be the first question asked
(or related, the password change one).
The answer is no: the 6h delay to get both databases in sync is still
required. They are perhaps options to tackle this in the future. Colin &
I will have a look.
But our priority for now was to sanitize the whole thing to let Jira 6
run on top of it.
On 06/10/2015 04:42 PM, Hermès BÉLUSCA - MAÏTO wrote:
Hi!
Happy to hear that, I hope it fixes also this timeout that some people who just created a
new ROS account suffered when connecting to Jira for the first time?
Hermès.
-----Message d'origine-----
De : Ros-dev [mailto:ros-dev-bounces@reactos.org] De la part de Pierre Schweitzer
Envoyé : mercredi 10 juin 2015 16:34
À : ReactOS Development List
Objet : [ros-dev] Changes in authentication for Jira
Dear all,
We have proceed to a complete reimplementation of authentication server which serves Jira
& Fisheye. The purpose is to rely on something maintained and stable.
It should not change anything for you on daily usage. 58 accounts have been left out and
will not be able to connect to Jira due to incompatible account name (using invalid
chars). If you happen to be incapable of log in, please contact me so that I can rename
your account.
New accounts cannot be created with such invalid chars any longer.
As a side note, this was a major blocker for our upgrade to Jira 6. If we do not spot
anything wrong with our new authentication mechanism, then, then the upgrade to Jira 6
should happen in the next days.
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev
--
Pierre Schweitzer <pierre(a)reactos.org>
System & Network Administrator
Senior Kernel Developer
ReactOS Deutschland e.V.