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
Currently, the Clients (Connected*) doesn't support SSL CERT addition (SSL_CLIENT_AUTH_CERT). They should support a mechanism to pass HttpClient or ApiCLient so that the SSL context can be configured. This should be applicable for both Unauthorized as well as Authorized clients.
Rules
The client should support the HTTPS as well.
All repositories, registries, and aas environment should have this support.
The HTTPS should be applicable for authorized BaSyx server as well as Unauthorized (it means that TokenManager can also be configured).
Only adding the parameter for ApiClient or RepositoryApi inside ConnectedApi or AuthorizedConnected*Api might be sufficient.
mdanish98
changed the title
Client (Connected*) should also support HTTPS
Client (Connected*) should also support SSL CERT addition (SSL_CLIENT_AUTH_CERT)
Sep 27, 2024
mdanish98
changed the title
Client (Connected*) should also support SSL CERT addition (SSL_CLIENT_AUTH_CERT)
Client (Connected*) should also support SSL CERT addition or X.509 certificates (SSL_CLIENT_AUTH_CERT)
Sep 27, 2024
Currently, the Clients (Connected*) doesn't support SSL CERT addition (SSL_CLIENT_AUTH_CERT). They should support a mechanism to pass HttpClient or ApiCLient so that the SSL context can be configured. This should be applicable for both Unauthorized as well as Authorized clients.
Rules
Entry Points
Acceptance Criteria
Risks and Assumptions
References & Notes
Dependencies and Blockers
The text was updated successfully, but these errors were encountered: