Search Unity

  1. Unity 6 Preview is now available. To find out what's new, have a look at our Unity 6 Preview blog post.
    Dismiss Notice
  2. Unity is excited to announce that we will be collaborating with TheXPlace for a summer game jam from June 13 - June 19. Learn more.
    Dismiss Notice

Bug Access control not updating?

Discussion in 'Unity Gaming Services General Discussion' started by astorm608, May 5, 2024.

  1. astorm608

    astorm608

    Joined:
    May 4, 2024
    Posts:
    4
    HTTP/1.1 403 Forbidden HttpException: (403) HTTP/1.1 403 Forbidden
    Got these two errors. I denied all access to ugs and tried to write specificities of allowing some, but didn't quite work out yet, a lot of things stopped working. So I tried to allow all ugs, but after a long time the access was still denied.
    ugs access upsert-project-policy project-policy.json
    {
    "statements": [

    {
    "Sid": "allow-all-ugs",
    "Effect": "Allow",
    "Action": [
    "*"
    ],
    "Principal": "Player",
    "Resource": "urn:ugs:*"
    }
    ]
    }
    This is my policy right now. Any help would be appreciated.
     
  2. EricRobitaille-Unity

    EricRobitaille-Unity

    Unity Technologies

    Joined:
    Feb 12, 2021
    Posts:
    3
    Hi astorm608,

    Hopefully I can help you with this issue. I tried testing the
    allow-all-ugs
    statement you provided. With it, I was able to successfully call different services, so I don't think that the statement itself is the issue.

    My initial ask would be to double-check that the resource has been updated properly. You can run the
    ugs access get-project-policy
    and double check that the "Effect" value is set to "Allow".

    If you're still having issues, you could back up your current statement in a file, and do a
    ugs access delete-project-statements <path-to-delete-file>
    . The delete-file would look like this in your case

    {
    "statementIDs" : [
    "allow-all-ugs"
    ]
    }

    Let me know if you're still having issues and we can try to diagnose it further.

    Thanks,
    Eric
     
    GabKBelmonte likes this.