-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Login for real e2e tests #207
Comments
added script in this branch: https://github.com/js-soft/wdi5/tree/feature/e2eLogin maybe is misunderstood the requirements? |
hey 👋 - silence for 30 days 🤐 ... anybody? 😀 |
in the works |
might be contributed by QMate Team |
What's the actual state ? Will this roadmap step provide authentication for testing of users with differnent permissions / roles ? |
still WIP, with generic BTP login coming first. |
That means that the testuser will authenticate against the BTP and must exist there. As we're using an own IDP with certificate based login this will be a bit tricky, right? Will this scenario be supported? |
Hello colleagues, @vobu @dominikfeininger @T1mey, the priority of this ticket for our project is high now. It was raise on March, and we are unable to integrate our e2e tests in an automated jenkins job. |
there's been some back and forth on this topic - originally we thought that some SAP colleagues will contribute the authentication part, but that got stalled into the void.
with the standard IdP coming first. given the current track record, I'll refrain from promising any delivery dates. |
Hi, this issue has now been open for almost 7 months, with the last mention of it "being in the works" dating back to end of June. Very recently, during your Devtoberfest session on wdi5, @vobu, you reiterated that authentication features are "in the works". I see that it's part of the in progress roadmap, but is there any update on this? |
@monavari-lebrecht is leading the dev effort for this and still on it. |
authentication capabilities: - BTP SAP Cloud IdP - BTP Standard IdP - Office 365 - Basic Auth - custom auth fields authentication works for single browser scenarios as well as multiremote. credentials and authentication types are provided at design-time through configuration and don't require code changes. docs still todo, short version is: - standard: provide env vars `wdi5_username` and `wdi5_password` w/ respective values - multiremote: provide env var s`wdi5_$remote-id_username` and `wdi5_$remote-id_password` w/ respective values - add `wdi5:authentication` config object (see `src/types/wdi5.types.ts` → `*Authenticator`) to the `capabilities` section of the `wdio.conf.(t|j)s` file addressing #207 Co-authored-by: scoen <[email protected]> Co-authored-by: dominik.feininger <[email protected]> Co-authored-by: Constantin Lebrecht <[email protected]>
No description provided.
The text was updated successfully, but these errors were encountered: