CX Portal & IAM for local development Bricks after Login

[DavidNeuberger]

Current Behavior

After i Log into http://portal.tx.test CX-Operator with the credentials given on the Readme: User: [email protected]
User: tractusx-umbr3lla!

i get the following site

with the Error message

XHRGET
http://portal-backend.tx.test/api/registration/applications
[HTTP/1.1 401 Unauthorized 376ms]

	
GET
	http://portal-backend.tx.test/api/registration/applications
Status
401
Unauthorized
VersionHTTP/1.1
Transferred592 B (0 B size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem

    	
    Access-Control-Allow-Credentials
    	true
    Access-Control-Allow-Headers
    	DNT,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Authorization
    Access-Control-Allow-Methods
    	GET, PUT, POST, DELETE, PATCH, OPTIONS
    Access-Control-Allow-Origin
    	http://portal.tx.test
    Access-Control-Max-Age
    	1728000
    Connection
    	keep-alive
    Content-Length
    	0
    Date
    	Fri, 18 Oct 2024 09:55:04 GMT
    WWW-Authenticate
    	Bearer error="invalid_token", error_description="The signature key was not found"
    X-Request-Id
    	3626369e596a4e636bff514c393c45c5
    	
    Accept
    	*/*
    Accept-Encoding
    	gzip, deflate
    Accept-Language
    	en-US,en;q=0.5
    authorization
    	Bearer eyJhbGciOiJSUzI1NiIsInR5cCIgOiAiSldUIiwia2lkIiA6ICJSek51OWpZRUJmekZySWRnNF9mUTdkSFgtR2NwdDhKRmdaMkI3cmdDNGRzIn0.eyJleHAiOjE3MjkyNDU2MDQsImlhdCI6MTcyOTI0NTMwNCwiYXV0aF90aW1lIjoxNzI5MjQ1MzAzLCJqdGkiOiI2MGNmYjliZi0xMDg3LTQ3MzYtYmIzZi04MjEwM2E5NTNmYWIiLCJpc3MiOiJodHRwOi8vY2VudHJhbGlkcC50eC50ZXN0L2F1dGgvcmVhbG1zL0NYLUNlbnRyYWwiLCJhdWQiOlsiQ2wxLUNYLVJlZ2lzdHJhdGlvbiIsIkNsMi1DWC1Qb3J0YWwiLCJDbDE2LUNYLUJQRE1HYXRlIiwiQ2w3LUNYLUJQRE0iLCJDbDUtQ1gtQ3VzdG9kaWFuIiwidGVjaG5pY2FsX3JvbGVzX21hbmFnZW1lbnQiLCJDbDI0LUNYL…bWUiOiJhYzFjZjAwMS03ZmJjLTFmMmYtODE3Zi1iY2UwNTgwMjAwMDYiLCJnaXZlbl9uYW1lIjoiVGVzdCBVc2VyIiwiZmFtaWx5X25hbWUiOiJDWCBPcGVyYXRvciIsImVtYWlsIjoiY3gtb3BlcmF0b3JAdHgudGVzdCJ9.kaYo-Qw4HIfh3wef_7wbnAhUPH2CED2QRyF1g8XQgT67czrIRZ8hV6WuV7GzdN7tEtumHoPREebBT4pTkiPBjcdldmnuUhBIb0IIMy_-BjXxsQeoUppL7_PtPTgKgvKO_KMawjCgnE8i5aKKyYkvBGiDs1A5JSztQfy1wdkuHlbQGC00ytmp6TH8DuslvLcCileNaEVKXeHjjA8fGWcqU2yHYHkt3R7-SYjUieOokRuLEI3wwNE-HVB-ve9NVoxP5c71nMsuFX6y_pVFv2qR42eSzZh6Zq2XWnsBcvF0CUA0C_XVrtqCl8fZ_c4-75_DRtQ8sJ0GUMunluCCF5M62g
    Connection
    	keep-alive
    DNT
    	1
    Host
    	portal-backend.tx.test
    Origin
    	http://portal.tx.test
    Priority
    	u=4
    Referer
    	http://portal.tx.test/
    User-Agent
    	Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:130.0) Gecko/20100101 Firefox/130.0

after that i can only access Keycloak and not Portal.tx.test until i restart the pods

Expected Behavior

After login I should have access to the Portal

Steps To Reproduce

Follow the "Setup of CX Portal & IAM for local development" README.md

[evegufy]

Hi @DavidNeuberger, thanks for reporting! So, when you restart the pods, the connection from the portal-backend to centralidp Keycloak works?

[DavidNeuberger]

Hi @evegufy,

Yes, I can open the portal again after restarting the pods or deleting the cookies. However, when I try to log in again, I encounter the same error screen.

It's worth noting that I'm running this on Windows with Minikube and Hyper-V. Additionally, I had to update the hosts file to match the IP shown in the Kubernetes ingress instead of the ip that is schown on the readme.