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

feat: allow user-specified default OkHttpClient instance #174

Merged
merged 1 commit into from
Apr 4, 2022

Commits on Apr 4, 2022

  1. feat: allow user-specified default OkHttpClient instance

    This commit modifies the java core so that users can now
    specify a fully-configured OkHttpClient instance to be
    used by service and authenticator instances:
    1. The HttpClientSingleton class now has methods setHttpClient()
       and getHttpClient().  These methods can be used to set and get
       the default client configuration from which other OkHttpClient
       instances are created.
    2. The TokenRequestBasedAuthenticator base class now has methods
       setClient() and getClient().  These methods can be used to set
       and get the specific OkHttpClient instance that should be used
       by an authenticator when interacting with the token service.
       These new methods are inherited by each of the request-based
       authenticator implementation classes: ContainerAuthenticator,
       CloudPakForDataAuthenticator, CloudPakForDataServiceAuthenticator,
       CloudPakForDataServiceInstanceAuthenticator, IamAuthenticator, and
       VpcInstanceAuthenticator.
    padamstx committed Apr 4, 2022
    Configuration menu
    Copy the full SHA
    91f86cb View commit details
    Browse the repository at this point in the history