Problem
The Asgardeo SDK ships a set of built-in UI components for each flow component type (password inputs, OTP fields, action buttons, social login buttons, etc.). Right now, the SDK is the only one that decides how each component type gets rendered — consumers have no way to influence this without modifying the SDK itself.
This creates two gaps:
-
Replacing built-in rendering — A consumer may want to use their own design system or branded component for a known type (e.g. substitute the built-in password field with their own). Currently they cannot do this without forking the rendering layer.
-
Handling unknown types — A server may emit a custom or non-standard component type that the SDK doesn't know about. Today, these are silently dropped. Consumers have no hook to provide rendering for types the SDK doesn't cover.
Proposed Solution
Allow SDK consumers to register custom render functions for any component type — known or unknown — so the SDK's rendering layer is open for extension without requiring changes to the SDK itself.
Alternatives
N/A
Please select the package issue is related to
@asgardeo/javascript
Version
"N/A"
Reporter Checklist
Problem
The Asgardeo SDK ships a set of built-in UI components for each flow component type (password inputs, OTP fields, action buttons, social login buttons, etc.). Right now, the SDK is the only one that decides how each component type gets rendered — consumers have no way to influence this without modifying the SDK itself.
This creates two gaps:
Replacing built-in rendering — A consumer may want to use their own design system or branded component for a known type (e.g. substitute the built-in password field with their own). Currently they cannot do this without forking the rendering layer.
Handling unknown types — A server may emit a custom or non-standard component type that the SDK doesn't know about. Today, these are silently dropped. Consumers have no hook to provide rendering for types the SDK doesn't cover.
Proposed Solution
Allow SDK consumers to register custom render functions for any component type — known or unknown — so the SDK's rendering layer is open for extension without requiring changes to the SDK itself.
Alternatives
N/A
Please select the package issue is related to
@asgardeo/javascript
Version
"N/A"
Reporter Checklist