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

403 when non-admin tries to get a team #179

Closed
gempain opened this issue Jan 7, 2021 · 5 comments
Closed

403 when non-admin tries to get a team #179

gempain opened this issue Jan 7, 2021 · 5 comments
Assignees
Labels
bug Something isn't working
Projects

Comments

@gempain
Copy link
Contributor

gempain commented Jan 7, 2021

Following the comment from @robertorubioguardia.


HI @gempain

I managed to add GitHub authentication and accept the invite following your instructions and then added the user as a member of a team in my organization, with no admin powers.

Thing is, when I log in from the new invited user, I get a 403 error in the GUI where the teams should be listed.
The API error in the console is:

{
"statusCode": 403,
"path": "/api/v1/teams/b6ddb484-0feb-4ae7-bf78-45aeaed6f67f/sites",
"message": "Cannot get team"
}

If I add the user to the team with admin powers, there is no error. I have also confirmed the team ID is valid.

Cheers.

@gempain gempain self-assigned this Jan 7, 2021
@gempain gempain added the bug Something isn't working label Jan 7, 2021
@gempain gempain added this to In progress in main Jan 7, 2021
gempain pushed a commit that referenced this issue Jan 7, 2021
# [1.0.0-beta.12](v1.0.0-beta.11...v1.0.0-beta.12) (2021-01-07)

### Bug Fixes

* add missing team member index ([bdcee5a](bdcee5a))
* prevent duplicate team members ([3eeaeaa](3eeaeaa))
* team member cannot read team and sites ([#179](#179)) ([8a56c94](8a56c94))
* wrong member selected for listing teams when multiple orgs ([03c5d3f](03c5d3f))
@gempain
Copy link
Contributor Author

gempain commented Jan 7, 2021

@robertorubioguardia a fix has been released in v1.0.0-beta.12. Can you confirm this is working for you ?

@robertorubioguardia
Copy link

Hi mate.

I did a docker system prune to delete all images, then docker-compose down and up again and the problem persists.

Am I missing something to get the latest code?

Cheers,

@gempain
Copy link
Contributor Author

gempain commented Jan 7, 2021

I don't think doing a system prune helps in this case, at least not in the order you mentioned. To pull the latest images, all you have to do is:

docker-compose pull
docker-compose up -d

There's no need to down anything 😄

@robertorubioguardia
Copy link

Hi @gempain

Thanks mate 😆 I am new in dockerland and still fiding my way around it.

The fox worked like a charm.

Is it ok if I keep coming with issues, etc? I am really into Meli but dont want to bug you too much :)

@gempain
Copy link
Contributor Author

gempain commented Jan 8, 2021

@robertorubioguardia I'm glad it helped ! Docker and Docker Compose are awesome, I'm sure you'll love it 😄

You are very welcome to open as many issues as you want. It helps other users that might have the same issues as you. You may as well join our chat if you'd just like to ask general questions. I'd be happy to learn about why you're using Meli and how it helps you, so head out here 🚀

I'll close this issue, but you may continue replying and we will reopen if needed.

Enjoy Meli !

@gempain gempain closed this as completed Jan 8, 2021
@gempain gempain moved this from In progress to Done in main Jan 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
main
Done
Development

No branches or pull requests

2 participants