[Epic]: New typescript Login with OIDC flow Deployed

[hifabienne]

As a end user I want to have the possiblity to deploy a ready to use login, and connect it to my ZITADEL instance.
Our goal is to have a first version ready, which can be selfhosted and does include the OIDC Standard.

Tasks for deploy login to vercel:

• OIDC: Proxy #48
• Security Headers (CSRF, etc.) #47
• Implement Basic Scopes #49
• tests for implemented flows (username password) #51
• Guide How to setup vercel and deploy to vercel button #50
• Guide for different use cases (hosted login, customize hosted login, your own login in your application)
• Guide about how to only change the styling of the login

Tasks login ready with state of current hosted login:

• Login: Register MFA #15
• Login: Login with MFA #18
• Login: Login with IDP #17
• Login: implement missing identity provider for register #37
• Implement missing scopes (metadata, roles, etc...)
• Use User API v2 in Management Console zitadel#8976
• Login: Handle invite user flow #166
• Test Cases #199

Excluded

In the first version the following things will be excluded, but be implemented right after

• SAML
• Device Authorisation Flow
• Multi-tenancy (Needed to run the login for our Cloud offering)

[muhlemmer]

Regarding this issue, planning and roadmap. We need something better..

• tests for implemented flows (username password) #51 has 3 days estimated and is already taking way longer and as we found out, not all items are being worked on.
• Guides are not planned yet
• Works resulting from Test Cases #199 are not estimated

There is a verbal agreement on deploying within Q1-2025 but I struggle to understand how many engineering hours it is going to take. I would very much appreciate if we can have issue for each feature the new login still needs. So we can plan and track our process and have deliverables we can demo each sprint.