Configure OAuth2 Application/Provider for TPLink Omada Controller using the client id/secret provided by omada

[cheggerdev]

Describe your question/
Configure OAuth2 Application/Provider for TPLink Omada Controller Version 5.14 using the client id/secret provided
by omada and not from authentik.
Can you help me out here?

Screenshots
If applicable, add screenshots to help explain your problem.

Version and Deployment (please complete the following information):

• authentik version: 2024.10.4
• Deployment: docker-compose

Additional context
Omada Controller Documentation how to use Open API:
https://omada-northbound-docs.tplinkcloud.com/#/home

The special thing here is the configuration works up-side-down:
The Omada Controller provides a client id and a client secret to be used by authentik,
while I am used to use the client id/secret from authentik provider.

[cheggerdev]

I need some guidance in how to connect an authentik Application with the Omada Controller (OC200/300).
I want to use Authentik as the IdP and not Omada.
Anyone who can help me?

[cheggerdev]

New Omada versions added SAML support.
Closing this in favour of #14508