Add service to service authentication

[lakshayman]

Add Authentication to Identity Service

Issue Description

The Identity Service currently lacks authentication mechanisms, making it vulnerable to unauthorized access. We need to implement authentication to secure service-to-service communication, particularly for requests from the website backend service.

Expected Behavior

• All endpoints in Identity Service should require authentication
• Unauthorized requests should be rejected with appropriate status codes
• Authentication mechanism should be scalable and maintainable
• Different authentication levels/permissions for different environments
• Proper logging of authentication failures

Current Behavior

• Endpoints are accessible without authentication
• No access control mechanisms in place
• No request validation for service identity
• No security measures for service-to-service communication

Screenshots

• Current endpoint configuration showing no authentication
• Service architecture diagram highlighting security gap
• Example of unrestricted access

Reproducibility

• This issue is reproducible
• This issue is not reproducible

Steps to Reproduce

1. Deploy Identity Service
2. Make a request to any endpoint
3. Observe that the request succeeds without any authentication validation
4. Verify that no authentication headers/tokens are required

Implementation Requirements

1. Research and select appropriate authentication mechanism
2. Update service configuration to enable authentication
3. Implement authentication validation
4. Add proper error handling
5. Update documentation
6. Add monitoring for authentication failures

Severity/Priority

• Critical
• High
• Medium
• Low

Additional Information

Key considerations for authentication implementation:

• Must be secure and follow best practices
• Should not significantly impact performance
• Must be easy to maintain and update
• Should support future scaling requirements
• Must include proper logging and monitoring

Technical Considerations

• Authentication credentials must be securely stored
• Implementation should follow SOA principles
• Should support different environments (dev/staging/prod)
• Must include proper error handling
• Should be easily integrable with other services

Checklist

• I have read and followed the project's code of conduct
• I have searched for similar issues before creating this one
• I have provided all the necessary information
• I am willing to contribute to the resolution of this issue

Testing