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

Can't change WhoCanJoin attribute on Update-GSGroupSettings #9

Closed
WillieWookiee opened this issue Jan 24, 2018 · 6 comments
Closed
Assignees
Labels

Comments

@WillieWookiee
Copy link

WillieWookiee commented Jan 24, 2018

I am attempting to change the whoCanJoin attribute via the Update-GSGroupSettings cmdlet and it does not change. I don't even get an error.

I know that I am authorized because I can change any other attribute and it works.

I get a response back from the API with no error code, but the attribute is not changed. The command I am running is:

update-GSGroupSettings -group group@domain.com -WhoCanJoin "ALL_IN_DOMAIN_CAN_JOIN"

If someone wouldn't mind testing that would be awesome. I am not sure if it is a pre-requisite issue or what.

@scrthq
Copy link
Member

scrthq commented Jan 24, 2018 via email

@WillieWookiee
Copy link
Author

In further testing, I am leaning towards a Google API issue. I have tried just using Fiddler to PATCH the request to Google and it still doesn't update.

I am going to open a case with them.

@scrthq
Copy link
Member

scrthq commented Jan 24, 2018 via email

@WillieWookiee
Copy link
Author

Nate, if you wouldn't mind testing it on your end, that would be awesome.

I have contacted Google and opened a case, but they will need to get back with me. Thanks!

@WillieWookiee
Copy link
Author

Nate, no need to test now. I just heard back from Google and they confirmed it is a bug (70841287).

They hope to have a resolution by the end of the day. Thanks for the quick responses and awesome powershell module!

@scrthq scrthq self-assigned this Jan 24, 2018
@scrthq scrthq added the vendor label Jan 24, 2018
@scrthq
Copy link
Member

scrthq commented Jan 24, 2018

Awesome! Thanks for the update, glad it's hopefully going to be a quick fix on the vendor side! Closing this down 👊

@scrthq scrthq closed this as completed Jan 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants