Tenant Connection, Login, and Profiles

A tenant needs both network reachability to the tenant-facing GWEB services and an authorized tenant identity.

Tenant connection

Use the connection method assigned by GWEB during onboarding.

Depending on the tenant and enabled services, GWEB may provide:

• normal tenant-facing service access; or
• tenant-specific VPN/private access.

If tenant VPN access is enabled, GWEB provides the tenant-specific connection material separately. Administrative or infrastructure-management VPN access is not part of the tenant workflow.

See Tenant Connection, VPN and Service Access for the tenant network model.

Login

Run:

gwebc auth login

The CLI uses the tenant's configured identity flow.

Check the result:

gwebc auth status

Capabilities

After login:

gwebc capabilities

Capabilities are tenant-scoped and do not grant cluster-admin access.

Profiles

A profile identifies the tenant/account context used by gwebc.

For the current GEDU validation workflow:

gwebc --profile gedu ...

Use the profile assigned to your tenant. A profile does not grant permissions by itself; authorization still depends on the authenticated tenant identity and platform policy.

Safety

Never share:

• access tokens;
• refresh tokens;
• local session files;
• tenant VPN private keys;
• service credentials;
• GWEB platform credentials.

gwebc does not require GWEB platform-administrator credentials.