Closed AlexanderNeumann closed 2 years ago
fyi When starting a local las2peer network, for example with the Distributed Noracle Services, the problem does not occur. So maybe it is only related to the las2peer developer network (las2peer-bootstrap.sbf-dev)?
When I visit https://git.tech4comp.dbis.rwth-aachen.de/las2peer/webapp/welcome , I get the error:
We are sorry...
Invalid parameter: redirect_uri
When trying to log in
If I understood it correctly, that is the issue of the agent id not being correct which is fixed in https://github.com/rwth-acis/las2peer/pull/125 (, please correct me @Aran30 if that's not the case.)
Can you update the repository (https://archiva.dbis.rwth-aachen.de:9911/repository/internal/i5/las2peer-bundle/) with the las2peer version of 1.2.1? Then I can test, if this solves the problem.
We updated las2peer on the dev network. It seems like this problem still persists. I could only log in the first time after restart. After that, I got the agent not found error. The oidc sub is unknown. The logs on the bootstrap container show
2022 Jan 30 18:27:47 INFO i5.las2peer.connectors.webConnector.util.AuthenticationManager: attempting login with id: OIDC_SUB-undefined
2022 Jan 30 18:27:47 FINER i5.las2peer.p2p.PastryNodeImpl: ARTIFACT_FETCH_STARTED (2060) <0xDCED12..>//137.226.232.175:32011:las2peer-bootstrap-7db6dd55c7-8wvxz/10.244.0.196:32011
For my test account, I received the same agent when I called https://git.tech4comp.dbis.rwth-aachen.de/las2peer/currentagent
Turns out the problem stemmed from weirdly configured access rights to the persistent storage. It now works again.