feat(ui): create SignInForm component

[vlad-schur-external-sap]

Summary

Created a SignInForm component that can be used to render consistent, configurable Sign In forms according to the visual design in Figma.

Changes Made

• Added SignInForm Component
• Added corresponding stories to the component with the most used customer scenarios
• Added tests

Related Issues

• Issue 1439: [Task](ui): create SignInForm component #1439

Screenshots (if applicable)

SignInForm component documentation

SignInForm stories

Checklist

• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• I have made corresponding changes to the documentation (if applicable).
• My changes generate no new warnings or errors.
• I have created a changeset for my changes.

PR Manifesto

Review the PR Manifesto for best practises.

[changeset-bot]

🦋 Changeset detected

Latest commit: 830c110

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 9 packages

Name	Type
@cloudoperators/juno-ui-components	Minor
@cloudoperators/juno-app-carbon	Patch
@cloudoperators/juno-app-doop	Patch
@cloudoperators/juno-app-example	Patch
@cloudoperators/juno-app-greenhouse	Patch
@cloudoperators/juno-app-heureka	Patch
@cloudoperators/juno-app-supernova	Patch
@cloudoperators/juno-app-template	Patch
@cloudoperators/juno-messages-provider	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2026-02-13 14:22 UTC

[franzheidl]

Hey @vlad-schur-external-sap ,

thanks so much! Here's a couple of things:

1. Thought about the story with only one button (external auth), I think we should remove it. The decision whether to render a form or just the button is not a concern of the SigninForm itself, but of the surrounding page/app.
   This case will be reflected when we build the templates in a later task.
2. Please change the PR title to something that fits our requirements, so the PR can actually pass our checks and can be merged, e.g. "feat(ui): add SignInForm component".
3. Please add a changeset.
4. Un-draft the PR so it can be reviewed and merged.
5. Write a quick summary, one-liner is fine in this case IMO.

Any questions, hit me up.

[franzheidl]

Ah sorry, my bad, PortalProvider may be needed for Select, I wasn't thinking. 😓

[ArtieReus]

Great!! I like it very much. Just added some comments to discuss...

[ArtieReus]

everything ok from my side :)

[edda]

👍 🚀