You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I see SDK does give an option in RequestContext to pass the user-agent to Okta in primary authentication endpoint. But we have requirement of custom user-agent to see in Okta sys logs for every call done to Okta. Hence requesting you to enhance this for all the endpoints(i.e., 2FA, change password etc.,) in SDK to pass the custom user-agent which allows Okta to read the custom value passed from application using SDK instead of fixed user-agent value that is being passed from Okta IDX Dotnet SDK.
And current SDK implementation is accepting user-agent as a string where we don't have an option to pass Browser, OS, RawUserAgent values individually. So supporting user-agent as a Object/Class with mentioned values will be quite helpful!
New or Affected Resource(s)
NA
Provide a documentation link
No response
Additional Information?
No response
The text was updated successfully, but these errors were encountered:
Describe the feature request?
I see SDK does give an option in RequestContext to pass the user-agent to Okta in primary authentication endpoint. But we have requirement of custom user-agent to see in Okta sys logs for every call done to Okta. Hence requesting you to enhance this for all the endpoints(i.e., 2FA, change password etc.,) in SDK to pass the custom user-agent which allows Okta to read the custom value passed from application using SDK instead of fixed user-agent value that is being passed from Okta IDX Dotnet SDK.
And current SDK implementation is accepting user-agent as a string where we don't have an option to pass Browser, OS, RawUserAgent values individually. So supporting user-agent as a Object/Class with mentioned values will be quite helpful!
New or Affected Resource(s)
NA
Provide a documentation link
No response
Additional Information?
No response
The text was updated successfully, but these errors were encountered: