Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support OAuth2.0 Flows #31

Open
sebbader-sap opened this issue Jun 20, 2024 · 3 comments
Open

Support OAuth2.0 Flows #31

sebbader-sap opened this issue Jun 20, 2024 · 3 comments

Comments

@sebbader-sap
Copy link

I was not able to find whether the test engine can already send access tokens to the system under test. As enterprise systems usually do not even offer the option to interact without any kind of authentication (also basic authentication or username/password is not sufficient), the test engine cannot be used.

Proposal

Given that I am not missing anything obvious: Add support for OAuth2 flows. Enable the user to configure client id, secret, and auth server.

@sebbader-sap
Copy link
Author

The AAS specification does not define any required authentication pattern, of course. I am not asking for an evaluation of the implemented auth flows. Rather, I want to use the test engine to also for solutions that do not allow any incoming request without any user information.

@otto-ifak
Copy link
Collaborator

Hi @sebbader-sap, that is a good idea. Is there any open source implementation we could test this against?

@sebbader-sap
Copy link
Author

I am not aware whether any of the currently available open source AAS server implementations have a proper user management. However, I can certainly offer my company's test and demo instances. Just send me an email ([email protected]) and we can align on the details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants