Account & security

Your Gewape ID account

Gewape ID is the single account you use across Gewape Cloud. One login signs you in to the console and your other Gewape services, so there is one password and one place to manage your security. Manage it at https://sso.gewapecloud.com/realms/gewape/account. What you manage there - Profile: your name and contact details. - Password: change it whenever you need to. - Two-factor authentication: turn it on and manage your authenticator app and recovery codes. - Active sessions: see where you are signed in and sign out devices you do not recognise. Why it is separate from the console The console (platform.gewape.cloud) is where you build and run cloud resources. Gewape ID is the identity behind your sign-in, so your password and security settings live in the Gewape ID account, not under the console's own menus. This keeps your identity consistent across every service. Common tasks - Sign in to the console - Turn on two-factor authentication - Reset your authenticator app - Invite team members and set roles If you forget your password, use the "Forgot password" link on the sign-in page to reset it by email.

Turn on two-factor authentication

Two-factor authentication (2FA) adds a second step to signing in: after your password, you enter a 6-digit code from an app on your phone. It is the best protection against someone getting into your account with a stolen password, and it takes about a minute to set up. Set it up 1. Go to https://sso.gewapecloud.com/realms/gewape/account and sign in. 2. Open Account security, then Signing in. 3. Under Authenticator application, choose Set up authenticator application. 4. Scan the QR code with an authenticator app (Google Authenticator, Authy, Microsoft Authenticator, or similar) and enter the 6-digit code to confirm. Save your recovery codes When you turn on 2FA, Gewape ID shows a set of one-time recovery codes. Save them somewhere safe and private. If you ever lose your phone, any one of them lets you sign in without waiting for support. Changing phones later, or lost your device? See How to reset your authenticator (2FA) app.

Invite team members and set roles

You can invite colleagues into your account so a team shares the same cloud resources, each signing in with their own Gewape ID rather than a shared password. Roles - Administrator: manage everything, including other members and billing. - Engineer: create and manage cloud resources, but not account-level settings. - Viewer: look but not change, which suits auditors or stakeholders. Invite someone 1. Open the team or members area of the console. 2. Choose to add a member and fill in: - Email: their work email. They will sign in with their own Gewape ID. - Role: pick the least access they need to do their job. 3. Send the invitation. They receive an email and set up their sign-in. Keep it tidy Review the member list from time to time so access leaves with people who do. To remove someone, open their entry and remove them; their access ends immediately. For automation and scripts, do not share a person's login; use an Application Credential instead.

API access and Application Credentials

Anything you can do in the console you can also do from scripts, Terraform, or the command line, using an Application Credential rather than your password. It is a pair of values (an ID and a secret) that stands in for your login, can be scoped to read-only, and can be revoked without touching your account. Create one 1. In the console, open the credentials area under your account. 2. Fill in: - Name: a clear label, such as terraform-ci. - Roles / scope (optional): limit it to read-only for anything that only inspects. - Expiry (optional): set a date if it should stop working automatically. 3. Create it and copy the secret now. It is shown once and cannot be retrieved later. Use it Put the ID and secret in a clouds.yaml file, and the standard OpenStack tools, Terraform, and SDKs will use it. Region endpoints, examples, and the full technical detail are in the developer documentation at developers.gewape.cloud. Treat the secret like a password: store it in a secrets manager, never commit it to code, and rotate it from time to time. If one ever leaks, revoke it here and create a new one.