Skip to content

Conversation

SomkaPe
Copy link
Contributor

@SomkaPe SomkaPe commented Jan 19, 2019

Making api more consistent and expressive

* Token, Refresh Token and the Access Token's expiration time.
*/
public CompletableFuture<AuthenticationResult> acquireToken(String scopes, String username) {
public CompletableFuture<AuthenticationResult> acquireTokenByKerberosAuth(String scopes, String username) {
Copy link
Contributor

Choose a reason for hiding this comment

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

yKerberosAuth [](start = 64, length = 13)

Isn't this called IntegratedWindowsAuth in the .NET SDK?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes, but these cased are different , Kerberos is platform agnostic

Copy link
Contributor

@henrik-me henrik-me left a comment

Choose a reason for hiding this comment

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

:shipit:

* property will be null for this overload.
*/
public CompletableFuture<AuthenticationResult> acquireToken(final String scopes) {
public CompletableFuture<AuthenticationResult> acquireTokenForClient(String scopes) {
Copy link
Contributor

Choose a reason for hiding this comment

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

acquireTokenForClient seems a bit redundant. Is there a reason why we want to swtich from acquireToken to acquireTokenForClient?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

to be consistent with .NET naming

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

Successfully merging this pull request may close these issues.

3 participants