use token as auth

[refaelm92]

User description

Signed-off-by: refaelm [email protected]

---

PR Type

Bug fix

---

Description

• Fixed authentication flow by returning the original authentication token instead of attempting to extract it from cookie
• Maintains consistency in token handling throughout the authentication process
• No changes to the overall login flow structure

---

Changes walkthrough 📝

	Relevant files
Bug fix	api_login.py Fix authentication token return value                                        infrastructure/api_login.py Fixed authentication token handling by returning the original auth token instead of extracting it from cookie +1/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Token Exposure: The code returns the raw authentication token as part of the response. This could potentially expose sensitive authentication credentials if the response is logged or not properly handled by the calling code. Consider whether returning the raw token is necessary for the authentication flow and if it can be securely handled by all consumers.

⚡ Recommended focus areas for review Token Validation Verify that returning the raw auth token instead of extracting it from cookie maintains the expected token format and doesn't break token validation downstream

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible issue	Fix incorrect Bearer token format in Authorization header to ensure proper authentication Verify that auth is a valid token string before using it in the Bearer header. The current format 'Bearer: {auth}' has an incorrect colon that breaks the Authorization header format. infrastructure/api_login.py [72] -response = self.session.get(f'{self.base_url}{API_OPENID_CUSTOMERS}',headers= {'Authorization': f'Bearer: {auth}'}) +response = self.session.get(f'{self.base_url}{API_OPENID_CUSTOMERS}',headers= {'Authorization': f'Bearer {auth}'}) Apply this suggestion Suggestion importance[1-10]: 9 Why: The suggestion correctly identifies a critical authentication issue where the Authorization header format is incorrect due to an extra colon after 'Bearer'. This could cause authentication failures in production.	9

[github-actions]

Failed to generate code suggestions for PR