Maia Iyer

Closes #411 This PR creates two new plugin types that separates the authentication and authorization pieces. This deprecates the older `auth` plugin type

This will probably create a major bump from Tornjak 1.x to 2.x Best practices for API design dictate an API should be versioned so as not to break functionality for...

Now that we are starting to support OIDC plugin and authorization logic configurability, upon k8s deployment, it is not always the case there is an endpoint exposed for k8s to...

Backend crashes upon disconnect with IAM server

2

upon temporary disconnect, backend should be able to re-connect with IAM server. Reported behavior states it crashes when the IAM server goes down.

This is to enables future development on pluggable authorization logic.

Federation feature for single Tornjak/SPIRE instance

1

We would like to extend Tornjak to make the Federation management experience easier. This involves backend decision of using the SPIRE API or potentially the controller manager CRDs. The frontend...

Now that CRDs have become a standard way to interact with SPIRE and the SPIRE controller manager, it may be a good feature to be able to manage the CRDs...

Clean up backend error handling

3

Some errors in the backend are very nested and as result less readable and a bit opaque. For example: ``` 2024/04/04 14:23:00 Cannot Configure: Cannot configure auth plugin: Couldn't configure...

Rename KeycloakAuth to OIDCAuth

1

Now that the backend has been generalized to be OIDC compatible, we will rename the plugin to OIDCAuth

Clean up Docs

1

Currently difficult to find documentation for each component. There are some redundant diagrams in different documents. Also want to make contribution guidelines more clear