a2aproject / a2aproject/a2a-dotnet
Security and SecuritySchemes sample
- Dominant language
- C#
- Stars
- 262
- Forks
- 64
- Avg merge
- 5d 2h
- Merged PRs (30d)
- 31
Description
Because when implementing and deploying the application with the A2A protocol, we normally need authentication/authorization.
I go to https://github.com/a2aproject/a2a-dotnet/blob/main/src/A2A/Models/AgentCard.cs#L88, https://github.com/a2aproject/a2a-dotnet/blob/main/src/A2A/Models/AgentCard.cs#L94, and the unit test at https://github.com/a2aproject/a2a-dotnet/blob/main/tests/A2A.UnitTests/Models/AgentCardTests.cs#L61 doesn't reflect how we can use these attributes in applications using A2A.
That would be great if we could have an example or guidance on how to do authentication/authorisation with the A2A protocol.
Contributor guide
Research direction
Look at the Security and SecuritySchemes attributes in src/A2A/Models/AgentCard.cs lines 88 and 94, and the existing unit test in tests/A2A.UnitTests/Models/AgentCardTests.cs line 61. Understand how authentication/authorization is intended to work with the A2A protocol. Create a sample application or documentation that demonstrates practical usage of these attributes in a real scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100