Need an AuthenticationBuilder about okta-auth-java HOT 7 CLOSED

Great idea!
Currently you can chain the methods though, so something link:

AuthenticationRequest request = authenticationClient.instantiate(AuthenticationRequest.class)
                .setRelayState("some-relay-state")
                .setUsername("[email protected]");

It requires a few extra lines though, are you thinking something like:

AuthenticationRequest request = AuthenticationRequestBuilder.instance()
                .setRelayState("some-relay-state")
                .setUsername("[email protected]")
                .build();

To customize the user-agent just implement a UserAgentProvider similar to this one: AuthnSdkUserAgentProvider

X-Forwarded-For is a little tricker, can you explain that use case in a little more detail?

from okta-auth-java.

Thanks, I found the instantiate method a little later on. Might be good to add to the readme. It's a viable work-around for now.

A small thing that I ran into with that was when instantiating a subclass, the order of setter calls matters:

// Works
client.instantiate(VerifyPassCodeFactorRequest.class)
  .setPassCode(passCode)
  .setStateToken(token);

// Does not compile
client.instantiate(VerifyPassCodeFactorRequest.class)
  .setStateToken(token) // returns a VerifyFactorRequest
  .setPassCode(passCode); // No such method on VerifyFactorRequest

My app is essentially acting as a login portal / gateway...
The X-Forwarded-For header requirement comes from the Okta API docs (See also.):

Okta supports the standard X-Forwarded-For HTTP header to forward the originating client’s IP address if your application is behind a proxy server or acting as a login portal or gateway.

Similarly, I need to set the User-Agent per request, which looks like it gets a bit tricky with the AuthnSdkUserAgentProvider:

If your application is acting as a gateway or proxy, you should forward the User-Agent of the originating client with your API requests.

from okta-auth-java.

@jmalickenexient no update yet.

Your comment will help us prioritize this though, Thanks!

from okta-auth-java.

All good points.
I'll get back to you on the headers 🤔

from okta-auth-java.

@bdemers What is the update on this? The ability to send a X-Forwarded-* header and User-Agent header containing the originating client User-Agent is needed to follow the Okta guidance on implementing a gateway application like @mfulgo mentioned.

from okta-auth-java.

@bdemers does this new README section cover what was needed by this issue? https://github.com/okta/okta-auth-java#setting-request-headers-parameters-and-device-fingerprinting

from okta-auth-java.

From my perspective, I think this issue is addressed with the RequestContext and the new README section.

from okta-auth-java.