# iYou Tech integration checklist

Product website: https://iyoucloud.com/

## 1. Confirm the application and its permissions

- Application name, purpose, and owner.
- Tenant, intended users, roles, and resource permissions.
- Client type: Web BFF, Web SPA, or native application.
- Ask an administrator to register the application and grant access. The portal does not offer anonymous self-service registration.

## 2. Configure authentication

- Application domains, allowed origins, exact callback URLs, and post-logout return URLs.
- Separate clients for local development and deployment. Do not use wildcard callback URLs.
- Obtain an administrator-assigned client ID. Confirm login templates, session policies, and step-up authentication requirements.
- OIDC issuer: https://sso.iyoucloud.com/realms/iyoucloud
- Discovery document: https://sso.iyoucloud.com/realms/iyoucloud/.well-known/openid-configuration
- Use Authorization Code + PKCE (S256) for Web SPA and native applications.
- BFF OAuth tokens stay on the server. Do not configure client secrets in browsers.
- Test the authentication protocol and business session integration together; a login redirect alone is insufficient.

## 3. Integrate the frontend platform

- Use Node.js >=22.13.0 <27 and pnpm.
- Obtain access to the @iyoucloud package registry, then pin platform runtime and tooling versions.
- Adopt application lifecycle, routing, themes, storage, and request capabilities as needed.
- Keep business models, permission codes, service endpoints, and brand design in the independent application.
- Admin applications can use default layouts. Websites and other products can define their own presentation layer.

## 4. Integrate services

- List application domains, upstream services, API paths, and required gateway policies.
- Define identity, session, tenant context, and server-side permission checks.
- Ask an administrator for application-authorized APIs for foundational services such as file storage.
- Do not include internal admin endpoints or service credentials in public frontend configuration.

## 5. Verify before launch

- Login, callbacks, restoration after refresh, recovery after expiration, and supported logout scopes.
- Role and tenant isolation, unauthorized access, API errors, and retries.
- Desktop and mobile layouts, light and dark themes, keyboard operation, and reduced motion.
- Type checks, tests, builds, post-deployment asset caching, and version rollback.

## System access

- Access Management: https://upms.iyoucloud.com/
- Authentication Center: https://auth.iyoucloud.com/
- Gateway Center: https://gateway.iyoucloud.com/

Access to every console depends on account permissions. Other foundational services are currently integrated through business applications or platform administration processes.
