Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    7
  • Answers answer
    1
  • Subscribers subscribers
    15
  • Views views
    646
  • Users 0 members are here
  • Locked Locked
Related
Options
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

AAuth 6.4.1.1 breaks windows Filr 5 client login

RaveNet
 

After upgrading to AAuth 6.4.1.1 and Filr 5.0.0.2, the windows Filr 5 client will no longer login as it won't move past the user.  Worked fine with aauth 6.4.1

not a google recapcha issue, only disabling aauth integration allows clients to login.

Web client works fine.

Anyone else seeing this?

Rodney

If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

  • 0

    Yes, I can confirm this. AA screen appears with username. But by clicking 'next' nothing happens.

  • 0

    Just filed a SR for this issue

  • 0  

    Was able to duplicate the issue.

    It seems the issue is caused by race conditions at the start of docker containers.

    Until development will address it with an update, it is fine to use a workaround (an example from my lab):

    1. Identify it is the same issue at your AAF server: these containers didn't start in my lab:

    # docker ps -a | grep Exited
    1517f31e900b mfsecurity/aaf-aucore:6.4.0.0 "/opt/run.sh" 5 days ago Exited (143) 2 minutes ago aaf-aucore-1
    fadb9b7d59e5 mfsecurity/aaf-radiusd:6.4.0.0 "/opt/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-radiusd-1
    048544595ee7 mfsecurity/aaf-afisd:6.4.0.0 "/opt/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-afisd-1
    6c0189dcd837 mfsecurity/aaf-audb:6.4.0.0 "/opt/entrypoint.sh …" 6 days ago Exited (128) 2 minutes ago aaf-audb-1
    44ee72394893 mfsecurity/aaf-searchd:6.4.0.0 "/run/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-searchd-1
    f10b2bb135f7 mfsecurity/aaf-repldb:6.4.0.0 "/opt/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-repldb-1
    b7159a8801b4 mfsecurity/aaf-fipsd:6.4.0.0 "/opt/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-fipsd-1
    4cf01502c447 mfsecurity/aaf-webauth:6.4.0.0 "/opt/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-webauth-1
    34221a0fea0a mfsecurity/aaf-webd:6.4.0.0 "/opt/run.sh" 6 days ago Exited (1) 2 minutes ago aaf-webd-1
    5992075ebcfe mfsecurity/aaf-redis:6.4.0.0 "/opt/run.sh" 6 days ago Exited (143) 2 minutes ago aaf-redis-1

    2. Start "first priority" containers 'aaf-webd-1' and 'aaf-redis-1' in given order:

    # docker start `docker ps -a | grep aaf-redis-1 | cut -c 1-12`
    # docker start `docker ps -a | grep aaf-webd-1 | cut -c 1-12`

    3. Start the other containers:

    # docker start `docker ps -a | grep Exited | cut -c 1-12 | sed ':a;N;$!ba;s/\n/ /g'`

    Enjoy! (only if all containers are started)
    until next reboot ;-)
  • 0 in reply to   

    Hello Mike,

    I notice that your version of AA is 6.4.0.0 and mine is 6.4.1.1. And when I do a 'docker ps -a|grep Exited'  I see no containers that are 'Exited'. All containers are 'Up'. So I do not think this solution works for me.

    Another addition: GroupWise on the same Windows PC with AA works fine.

  • 0   in reply to   

    I agree with  

    You are not running the same version of aauth as us.  This bug we are talking about came about in 6.4.1.1 which you are not running.  You appear to have a separate issue with your pods crashing which is causing a similar, but unrelated issue.

    Rodney

    If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

  • 0   in reply to   

    My apologies for the confusion and thank you for pointing out the images.

    It seems due the lack of disk space in my lab VM not all images were updated and as a result they are still 6.4.0.0
    Will need some time to re-configure VM and see how it goes with sufficient disk space

  • Suggested Answer

    0  

    Hi, Usually when you install a new version of software and Filr stops working it is the new software fault and not Filr :-)  My understanding is that the AA team is working on a fix.  However there is a patch that the Filr team have done to work around the problem which you can get from support.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.