You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to enhance the sign-in functionality to support custom headers in the login request. Currently, the headers parameter (signInHeaders) is optional and defaults to an empty object if not provided. However, we require the ability to pass specific headers during the sign-in process, which might be necessary for various use cases like API versioning, custom authentication tokens, or additional security measures.
Add Custom Headers: Ensure that custom headers can be passed into the signInHeaders parameter and included in the request. This will allow more flexibility for the client-side application to communicate with the backend.
Documentation: Update the documentation to reflect the inclusion of custom headers, including examples of how to use them effectively.
Testing: Implement unit and integration tests to verify that the headers are correctly passed and processed during the sign-in request.
Benefits
Flexibility: Enables the passing of custom headers, which can be crucial for meeting specific security and configuration requirements.
Scalability: Improves the scalability of the sign-in mechanism by allowing additional customization points without altering the core functionality.
Security: Supports the implementation of advanced security features by allowing headers to carry necessary authentication or verification tokens.
Additional information
Would you be willing to help implement this feature?
Provider
AuthJS
Local
Refresh
New Provider
The text was updated successfully, but these errors were encountered:
Describe the feature
We need to enhance the sign-in functionality to support custom headers in the login request. Currently, the headers parameter (signInHeaders) is optional and defaults to an empty object if not provided. However, we require the ability to pass specific headers during the sign-in process, which might be necessary for various use cases like API versioning, custom authentication tokens, or additional security measures.
How would you implement this?
Proposed Changes
Benefits
Additional information
Provider
The text was updated successfully, but these errors were encountered: