Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
- Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Before submitting a bug report, we ask that you first search existing issues and pull requests to see if someone else may have experienced the same issue or may have already submitted a fix for it.
Python Version & Okta SDK Version(s)
Python v3.13.3
okta 3.1.0
Affected Class/Method(s)
okta.models.group_profile.GroupProfile
Customer Information
Organization Name: Splunk
Paid Customer: yes
Code Snippet
from okta.models.group_profile import GroupProfile
j = '{"description": "All users in your organization", "name": "Everyone"}'
profile = GroupProfile.from_json(j)
print(profile.name)
Debug Output / Traceback
https://gist.github.com/ericli-splunk/fb3c0f249d93c874852f55626585822e
Expected Behavior
Everyone is printed in the terminal. This is the behavior of okta==3.0.0.
Actual Behavior
See AttributeError: 'GroupProfile' object has no attribute 'name'.
Steps to reproduce
- Run the code snippet provided above.
On okta==3.0.0, profile is:
GroupProfile(
description='All users in your organization',
name='Everyone',
additional_properties={}
)
However, on okta==3.1.0, profile is:
GroupProfile(
anyof_schema_1_validator=None,
anyof_schema_2_validator=None,
actual_instance=OktaUserGroupProfile(
description='All users in your organization',
name='Everyone',
object_class=None, additional_properties={}
),
any_of_schemas={'OktaUserGroupProfile', 'OktaActiveDirectoryGroupProfile'}
)
According to documentation, name should be a member of class GroupProfile.
To workaround this issue on okta==3.1.0, use print(profile.actual_instance.name) on line 4 instead.
References
https://github.com/okta/okta-sdk-python/blob/96ef4dc889098f2e95d4cd52b4e8ebd7f458da19/docs/GroupProfile.md
Community Note
Before submitting a bug report, we ask that you first search existing issues and pull requests to see if someone else may have experienced the same issue or may have already submitted a fix for it.
Python Version & Okta SDK Version(s)
Python v3.13.3
okta 3.1.0
Affected Class/Method(s)
okta.models.group_profile.GroupProfile
Customer Information
Organization Name: Splunk
Paid Customer: yes
Code Snippet
Debug Output / Traceback
https://gist.github.com/ericli-splunk/fb3c0f249d93c874852f55626585822e
Expected Behavior
Everyoneis printed in the terminal. This is the behavior ofokta==3.0.0.Actual Behavior
See
AttributeError: 'GroupProfile' object has no attribute 'name'.Steps to reproduce
On
okta==3.0.0, profile is:However, on
okta==3.1.0, profile is:According to documentation,
nameshould be a member of classGroupProfile.To workaround this issue on
okta==3.1.0, useprint(profile.actual_instance.name)on line 4 instead.References
https://github.com/okta/okta-sdk-python/blob/96ef4dc889098f2e95d4cd52b4e8ebd7f458da19/docs/GroupProfile.md