Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cast runasuser property to list, consider externaluser members #789

Closed

Conversation

fcarrus
Copy link

@fcarrus fcarrus commented Mar 18, 2022

  • Cast runasuser property from tuple to list

    The get method for ipasudorunas_user and ipasudorunasextuser returns
    a tuple instead of a list. Casting to list.

  • Consider externaluser members into user list

    The externaluser property was not taken into consideration while
    building the list of users to add to the sudorule.

  The get method for ipasudorunas_user and ipasudorunasextuser returns
    a tuple instead of a list. Casting to list.

* Consider externaluser members into user list

  The externaluser property was not taken into consideration while
    building the list of users to add to the sudorule.
Copy link
Member

@rjeffman rjeffman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these the only places where these changes are required?

What is the error you observed that you are trying to fix?

What was the context used, client or server?

user, res_find.get("memberuser_user"))
user,
(
res_find.get("memberuser_user", [])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When running with ipa_context: client, most member attributes are returned as tuples and not `list', so they need to be "cast" to list.

@t-woerner
Copy link
Member

A test for external users should be added.

@dkarpele
Copy link
Collaborator

A test for external users should be added.

#1020

@rjeffman
Copy link
Member

This change will be addressed by PR #1020. Thank you for bringing the issue to our attention.

@rjeffman rjeffman closed this Feb 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants