https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/AAA-101 aaa <p>aaa authn csit jobs see sporadic failures in test cases using token<br/> authentication. The recently (within 1s) retrieved token does not<br/> authenticate and the test REST call returns 401 and the test case<br/> fails.</p> <p>one job here:<br/> <a href="https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-only-boron/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/aaa/job/aaa-csit-1node-authn-only-boron/</a></p> <p>running the same suites locally produces the same failures. While <br/> reproducing, I used TRACE logging on org.opendaylight.aaa and saw<br/> these messages just after the failed token authentication happened:</p> <p>2016-05-04 00:00:21,915 | DEBUG | tp555984556-1669 | TokenAuthRealm | 212 - org.opendaylight.aaa.shiro - 0.3.2.Beryllium-SR2 | Authentication attempt using org.opendaylight.aaa.basic.HttpBasicAuth<br/> 2016-05-04 00:00:21,915 | DEBUG | tp555984556-1669 | IdmLightProxy | 223 - org.opendaylight.aaa.idmlight - 0.3.2.Beryllium-SR2 | get domain<br/> 2016-05-04 00:00:21,923 | DEBUG | tp555984556-1669 | AbstractStore | 222 - org.opendaylight.aaa.h2-store - 0.3.2.Beryllium-SR2 | Table DOMAINS already exists<br/> 2016-05-04 00:00:21,923 | DEBUG | tp555984556-1669 | DomainStore | 222 - org.opendaylight.aaa.h2-store - 0.3.2.Beryllium-SR2 | query string: prep257: SELECT * FROM DOMAINS WHERE domainid = ? </p> {1: 'sdn'} <p>2016-05-04 00:00:21,926 | DEBUG | tp555984556-1669 | IdmLightProxy | 223 - org.opendaylight.aaa.idmlight - 0.3.2.Beryllium-SR2 | check user / pwd<br/> 2016-05-04 00:00:21,926 | DEBUG | tp555984556-1669 | UserStore | 222 - org.opendaylight.aaa.h2-store - 0.3.2.Beryllium-SR2 | getUsers for: � in domain sdn<br/> 2016-05-04 00:00:21,942 | DEBUG | tp555984556-1669 | AbstractStore | 222 - org.opendaylight.aaa.h2-store - 0.3.2.Beryllium-SR2 | Table USERS already exists<br/> 2016-05-04 00:00:21,943 | DEBUG | tp555984556-1669 | UserStore | 222 - org.opendaylight.aaa.h2-store - 0.3.2.Beryllium-SR2 | query string: prep259: SELECT * FROM USERS WHERE userid = ? </p> {1: STRINGDECODE('\u 00ef\u00bf\u00bd@sdn')} <p>2016-05-04 00:00:21,945 | DEBUG | tp555984556-1669 | AuthenticationListener | 212 - org.opendaylight.aaa.shiro - 0.3.2.Beryllium-SR2 | Unsuccessful authentication attempt by � from &lt;snip&gt;</p> <p>I checked against Beryllium SR1, Lithium SR2 and the current Beryllium SR2 candidate. I ran<br/> the robot suite 40 times each and the results:</p> <p>BeSR2 - 8 failures<br/> BeSR1 - 11 failures<br/> LiSR2 - 0 failures</p> <p>email thread discussing this issue is here:</p> <p><a href="https://lists.opendaylight.org/pipermail/integration-dev/2016-May/006612.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/integration-dev/2016-May/006612.html</a></p> <p>Operating System: All<br/> Platform: All</p> AAA-101

token authentication fails intermittently

Bug Confirmed Unresolved zhengj ingwen Jamo Luhrsen Wed, 4 May 2016 00:06:11 +0000 Thu, 21 Mar 2019 11:56:46 +0000 General 0 2 <p>This does happen in Li-SR4 too; it took a little longer to present but it does happen. This isn't a regression, and I feel there may be a race condition in the ehcache implementation. Will look further later.</p> Development External issue ID 5838 External issue URL Rank 0|i0243r: