Skip to content

[Bug] pac admin create-service-principal assumes default environment admin #384

@ianjensenisme

Description

@ianjensenisme

Is there an existing issue?

  • I have searched the existing issues

Description

Errors like the one included below can occur when the user following the app registration setup instructions do not have user admin permissions on the default environment. There is a workaround, which is to run 'pac auth' against an environment that is not the default environment, but as the instructions stand, this is a real hurdle for users trying to set up the accelerator.

Error: Principal user (Id=<>, type=8, roleCount=<>, privilegeCount=<>, accessMode='', AADObjectId='', MetadataCachePrivilegesCount=, businessUnitId=<>), is missing prvCreateUser privilege (Id=<>) on OTC=8 for entity 'systemuser' (LocalizedName='User'). context.Caller=<>. Consider adding missed privilege to one of the principal (user/team) roles.

Steps to Reproduce

Expected Behavior

Run pac admin create-service-principal without errors.

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions