This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

uppercase / lowercase FQDN

Hi All

    My AA use uppercase letter as hostname when install.

after perform online update....user could not login user portal.

it show not match as screeshot.

I check DNS/hosts use lowercase letter, I also try to modify hostname by using yast.

but it still show the same result.

I think uppercase letter should be record in a file...but I do not know which file.

Could provie any suggestion to me ?

Thanks!!

Wencheng

Tags:

  • 0  

    Hello,

    What version of AAF is this?

    Thanks.

    Regards,

    Luciano Testa

  • 0 in reply to   

    HI  

         AAF is 6.4.2 

    Wencheng

  • 0   in reply to 

    Hello,

    Can you please send us this file from the appliance?


    /var/lib/docker/volumes/aaf_webauth-config/_data/WEB-INF/conf/current/TOP/tenantcfg.xml

    Thanks.

    Regards,

    Luciano Testa

  • 0 in reply to   

    Hi  

         Please check the attach zip file.

    I check it first...it indeed include uppercase FQDN.

    Wenchengtenantcfg.zip

  • 0 in reply to 

    Hi 

        I try to modify it to lowercase letter...and reboot appliance again.

    it show error that I need configure Public external URL messae again....

    but when I set it by setFQDN...it still show above message again.

    I change to set IP, 

    it still got the same error message (Uppercase/Lowercase) , and this tenantcfg.xml been change to uppercase FQDN again.

    wencheng

  • 0   in reply to 

    Hello Wencheng,

    Please open a ticket with Technical Support so we can better track this. We have to replicate this internally and see if there is a workaround or a fix is needed. Please mention in the new ticket this defect, so TS can refer to it if a defect is confirmed: OCTCR56A69579 .

    Thanks.

    Regards,

    Luciano Testa

  • 0 in reply to   

    Hi

       I had a case#02715315 which for internal Server error, it still keep open status.

    And this issue could be replicate in my lab

    Wencheng

  • 0   in reply to 

    Hello Wencheng,

    I was able to replicate this in my lab. I am also trying to get a workaround from Development.

    I am in contact too with the engineer in charge of the ticket so he is informed of the situation.

    For some reason I am able to contact the AAF server with its IP.

    Thanks.

    Regards,

    Luciano Testa

  • 0 in reply to   

    HI  

       Could I know your method how to use IP access user portal?

    Because even I set IP on Public external URL iin my lab which has same problem

    I use IP to open user portal...the URL will auto change to FQDN 

    after auth , I still meet the error message

  • 0   in reply to 

    Hello,

    I am sorry, still doesn't work with the IP. It worked for some time then it broke down again, but it was after I recreated the cluster, etc.

    Thanks.

    Regards,

    Luciano Testa