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
Unable to pass ClientSecret while configuring the client, the previous way shows that it have been deprecated. Current configuration initialisation does not have a separate parameter to pass client secret in init. Sending Secret in "additionalParameters" might or might not work as authentication is getting completed even without client secret of user in private application.
What is expected to happen?
Need a configuration constructor that accepts client secret as a parameter. Authentication flow should not succeed without client secret.
What is the actual behavior?
Separate parameter for client secret is already provided in previous versions of SDK but now its deprecated. Need to add a parameter for client secret in client configuration.
Reproduction Steps?
Create a private application in Okta tenent.
Get client secret and client id from tenent settings.
Add client id in "clientId" parameter and client secret in additional parameters in client configuration.
Check if authentication flow is working fine.
Now remove the additional parameters.
Check if authentication flow is going fine.(It should not work - but its working)
Additional Information?
No response
SDK Version(s)
3.0.8
Build Information
No response
The text was updated successfully, but these errors were encountered:
Hi @CityHunter07, @mikenachbaur-okta is working on this, but he is currently taking time off. He will update further once he is back from his time off.
Describe the bug?
Unable to pass ClientSecret while configuring the client, the previous way shows that it have been deprecated. Current configuration initialisation does not have a separate parameter to pass client secret in init. Sending Secret in "additionalParameters" might or might not work as authentication is getting completed even without client secret of user in private application.
What is expected to happen?
Need a configuration constructor that accepts client secret as a parameter. Authentication flow should not succeed without client secret.
What is the actual behavior?
Separate parameter for client secret is already provided in previous versions of SDK but now its deprecated. Need to add a parameter for client secret in client configuration.
Reproduction Steps?
Additional Information?
No response
SDK Version(s)
3.0.8
Build Information
No response
The text was updated successfully, but these errors were encountered: