Thank you. This worked. I was using JWT with Bearer and didn't realize I need to use q_session_user since I am using @Authenticated.

The interceptor checks if the backend call fails and then redirects to login. There are situations where we are loading a page without any backend calls. These are the dumb components that get loaded and when the user clicks on some button, the first backend call takes place, which then triggers the authentication logic through the interceptor.
Now if someone bookmarks a page or knows the urls, they are still able to load the page without having any authorisation to do so.
Which is why ...

Hmm danke, ich habe an das komplett vergessen. Allerdings funktioniert nun die Desktop API nicht:

http://localhost:4200/coloc/checkin/api/user/desktop

{status: 404, title: "Unknown error, status code 404",…}
status
:
404
title
:
"Unknown error, status code 404"
type
:
"exception:org.jboss.resteasy.client.exception.ResteasyWebApplicationException"

2022-09-16 09:34:54,192 INFO [io.qua.htt.access-log] (executor-thread-0) 127.0.0.1 - - 16/Sep/2022:09:34:54 +0200 "GET /coloc/...

Ja danke es hat mit subject.getDistinctAssignedRoleNames() geklappt.

So here fundamentally I have to use the quarkus.container-image.name in case I want to override the image name that you are providing by default. The other properties, like I said in the question before if i only change quarkus.container-image.registry-name, it is taking my username as the default, as the document says.
So I have to kind of hardcode the quarkus.container-image.name to include registry name, image name and tag name.
On a slightly different note, I still don't have a CI pip...

Here the problem was that when I was creating the application, I used
mvn archetype:generate
-DarchetypeGroupId=at.campusonline.conx
-DarchetypeArtifactId=co-supersonic-archetype
-DarchetypeVersion=1.3.0
-DgroupId=at.unigraz
-DartifactId=co-loc-checkin
-Dversion=1.3.0
-DurlPrefix=coloc/checkin
-DjdbcUrl=jdbc:oracle:thin:@ugo11.uni-graz.at:1521:kfuprod
-DdbUser=CO_LOC_CHECKIN
-DauthServerUrl=https://qline.uni-graz.at/QSYSTEM_KFU/co/public/sec...

I have used a third party package called Shedlock. Here the Containers fight over locking a table and then one of them gets the lock. The one that gets the lock will get to run the cronjob. It seems to work well so far :-).
https://github.com/lukas-krecan/ShedLock