Fix authentication issue causing 401 errors (clean) #175
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes the critical authentication issue that was causing all API calls to fail with 401 Unauthorized.
The Problem
authOptionsis a function that requires the request parameterauthOptionsinstead ofauthOptions(req)The Solution
Fixed
authOptionscalls in API endpoints:pages/api/requestOp.ts- Now callsauthOptions(req)pages/api/direct/models.ts- Now callsauthOptions(req)Added temporary mock responses for models endpoint:
Files Changed
pages/api/requestOp.ts- Fixed authentication, added mock responsespages/api/direct/models.ts- Fixed authenticationTesting
Security Note
This is a clean PR with no hardcoded secrets or credentials. The previous PR was closed due to accidental inclusion of build scripts containing secrets.