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

integrationTest: Add IT for user_token grant variants #2194

Merged
merged 7 commits into from
Aug 10, 2023

Conversation

strehle
Copy link
Member

@strehle strehle commented Feb 8, 2023

User Token Grant Type is proprietary grant type. Until now we dont have pure integration tests. therefore add with this PR one.
https://docs.cloudfoundry.org/api/uaa/version/76.18.0/index.html#user-token-grant

In PR
#2193
I noticed that no integration test has to be change but the PR is a restriction of current behavior

Because of the other PR I named the tests according to client types, e.g. public and/or confidential. A public client is a client without any secret or with an empty secret (like cf client). A confidential client is a client with a secure secret.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/184429062

The labels on this github issue will be updated when the story is started.

@strehle strehle changed the title Add IT for user_token grant [WIP] Add IT for user_token grant Feb 14, 2023
@strehle strehle marked this pull request as draft February 14, 2023 16:07
@Tallicia
Copy link
Contributor

Can we get a description on what this is addressing?

@strehle
Copy link
Member Author

strehle commented Jul 27, 2023

Can we get a description on what this is addressing?

created it to better understand what #2193 changes, so if we proceed with it, this test should be merged

The grant is similar to refresh but always without a secret.
The 4 examples are for the discussion about issue #2193
@strehle strehle marked this pull request as ready for review August 7, 2023 17:09
@strehle strehle changed the title [WIP] Add IT for user_token grant integrationTest: Add IT for user_token grant variants Aug 8, 2023
@strehle strehle mentioned this pull request Aug 8, 2023
@strehle strehle added this to the 76.19.0 milestone Aug 9, 2023
@strehle strehle added the expected behavior The isuse or PR is related to a RFC or other standard label Aug 9, 2023
@swalchemist
Copy link
Contributor

@strehle Does #2193 need to be merged before this one?

@strehle
Copy link
Member Author

strehle commented Aug 9, 2023

@strehle Does #2193 need to be merged before this one?

no the other way around, this should be merged first and then #2193 (after rebase) because then in PR you see what is not working anymore

Copy link
Contributor

@swalchemist swalchemist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few more minor comments. I'll go ahead and approve so you can take a look and then move ahead.

@strehle strehle merged commit 00a034e into develop Aug 10, 2023
18 checks passed
@strehle strehle deleted the userTokenIntegrationTest branch August 10, 2023 10:32
swalchemist pushed a commit that referenced this pull request Aug 17, 2023
* Add IT for user_token grant

* add more examples for user_token grant

The grant is similar to refresh but always without a secret.
The 4 examples are for the discussion about issue #2193

* refactor test cases

* test renamed

* review
Co-authored-by: Bruce Ricard <bricard@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
expected behavior The isuse or PR is related to a RFC or other standard
Projects
Development

Successfully merging this pull request may close these issues.

4 participants