Would it be possible to replace it with a link to how you suggest we call API's? Is the next step to use the API guide relevant to whichever API backend framework is preferred?
The reason this is not just straightforward as previously is because:
1) If you have a frontend application using client of type "SPA" you have a specific client ID for that application. Previously, you simply used that client ID on the server to verify the client.
2) Now that it seems the solution is to create a separate Server API client, you now have to create a separate client of type "Non-interactive" with a different Client ID.
3) So your server and client has now has different Client IDs, which is a more complex problem to solve than previously.
So now that the example of calling an API has been removed and no documentation has replaced it to solve this more complex problem.
This is relevant to commit a2484f0eb8b40eeae59e356ba0fe3a24bc4218c5
Why has the "calling API" example been removed?
Would it be possible to replace it with a link to how you suggest we call API's? Is the next step to use the API guide relevant to whichever API backend framework is preferred?
The reason this is not just straightforward as previously is because: 1) If you have a frontend application using client of type "SPA" you have a specific client ID for that application. Previously, you simply used that client ID on the server to verify the client. 2) Now that it seems the solution is to create a separate Server API client, you now have to create a separate client of type "Non-interactive" with a different Client ID. 3) So your server and client has now has different Client IDs, which is a more complex problem to solve than previously.
So now that the example of calling an API has been removed and no documentation has replaced it to solve this more complex problem.
This is relevant to commit a2484f0eb8b40eeae59e356ba0fe3a24bc4218c5