Idea Details

ROC: Fix Login Issues for LDAP users with certain characters in password

Last activity 06-13-2019 09:36 AM
Michael Gebhardt's profile image
05-20-2016 06:16 AM

Hey,

 

so, this might be hard for you without a german keyboard layout but we just did run into this issue again:

 

One person has changed his password yesterday and made it in a way that the character "ä" was in it, after this change he wasn't able to log into the ROC.

It took us quite some time to get to the root of this problem as he was able to log into automation studio!!

 

It seems that the login is treated differently in the java application as it is in the release operation center, so it would be nice, if both work kinda the same way.

 

We currently have a list of the following characters that should not be used (we assumed "ü" and "ö" won't work as well if "ä" doesn't): ä, ü, ö, ß and §

 

although we still have no idea, why the paragraph doesn't work. But we have an open case for that with CA: 208526 (seems like the "core team" is still working on it)

 

I'm just writing this now in the community to inform others of this issue.

 

Thanks.

 

Best Regards
Michael


Comments

06-02-2016 03:49 AM

appears to be a browser issue, could download it with firefox, weird

06-02-2016 02:05 AM

Hi Michael

I am not quite sure,maybe other non CA employees members can answer this one.

06-02-2016 01:45 AM

Hi Jacky,

 

thanks for the info, do you know if I need some kind of special permissions or so to download patches? because I always just get "550 no such file" (I tested now the links to the 6.1 patch, but also the 5.5.2 and 5.5.1)

 

I'm not taking the fact out of the equation that the ftp might be blocked from our system, but I am able to download from the download center.

 

thanks

michael

06-02-2016 01:20 AM

Hi

Just FYI - the new cumulative fix available to download in CA Release Automation Solutions & Patches - CA Technologies

Its include the fix for this issue.

Thanks

Jacky

05-30-2016 01:14 AM

awesome!

05-26-2016 09:16 AM

Moving this idea to the Delivered stage per tamme01's comment.

05-26-2016 03:39 AM

Yes. These characters are now supported

05-23-2016 02:34 AM

nice, we'll test it with the 6.1 update, when it comes out and can give you feedback if interested.

 

does the fix include all characters? so our german ä.ü.ö.ß and the §-sign?

the §-sign appeared to be a hard one as the case is open for quite some time now (well, could also be that it didn't have high priority in the backlog, which would be understandable )

05-22-2016 07:56 AM

Thanks Meir

05-22-2016 07:43 AM

Problem identified and resolved. Will be part of coming cumulative packs for both RA 5.5.2 and RA 6.1

05-22-2016 05:04 AM

Hi tamme01

Can you comment on this?

Thanks

Jacky

05-20-2016 09:02 AM

as I said, we already have an open case with CA regarding the "§" sign, I assume that this goes for the other characters as well...I just wanted to put it into the community to make it noticable for you guys as well and to get more attention back onto it. because I had the feeling, that I'm reaching more people in the community then with a ca ticket

05-20-2016 08:20 AM

Michael, I would consider this a bug, and open a support ticket.....