'RADIUS_FOR_CISCO_ASA' & 'AWS_FEDERATED_LOGIN' not recognized as valid ApplicationSignOnModes about okta-sdk-python

[laura-rodriguez]

Hi @mvitt,

Thanks for reporting this issue. We'll review this internally and provide you an update when we have more info to share.

[serhiibuniak-okta]

@mvitt, thanks again for detailed issue. Models are being generated according to our openapi spec. First, we need to update openapi spec. This requires some time. To unblock you, I can suggest some workarounds. For example, it is possible to get original response body (before it is being mapped to models):

apps, resp, err = await client.list_applications()
orig_resp = resp._body

And depending on your needs, you can filter failed apps or process manually or something else. Is it helpful?

[serhiibuniak-okta]

@mvitt After some internal discussions, we've decided to avoid errors so far by using "custom" signOnMode when we encounter any "new" signOnMode. Thus, sdk will pick basic Application model for such apps and list_applications won't fail.

Here's PR: #168. It will be added within next sdk release.

Please, reach out to us if you have any additional questions or concerns.

[serhiibuniak-okta]

@mvitt It turned out, there might be another issues related to signOnMode, thus a new PR should cover it: #174
It is merged and will be included into upcoming release. Will keep you posted.

[serhiibuniak-okta]

@mvitt SDK v1.4.1 released. I'm closing this issue as resolved. Feel free to reopen this issue if your problem still exists.