Open NV4RE opened 7 months ago
LINE LIFF (LINE Front-end Framework) is a tool provided by LINE, a messaging platform. It lets developers put their web apps directly inside the LINE app.
Here's how it works:
Integration in LINE App: With LIFF, developers can place their web apps inside the LINE app. This means users can use the web app without leaving LINE.
Authentication with LINE SDK: When users interact with the web app in LINE, LINE's authentication system checks their identity. This system gives the web app the user's LINE ID, a unique identifier.
Getting User Info: The web app gets the user's LINE ID. This ID helps the app recognize each user uniquely.
In short, LINE LIFF lets developers add their web apps to LINE. When users use these apps, LINE shares their ID, so the app can recognize them.
The reason we opt for LINE LIFF instead of directing users to our website is because people here predominantly use the LINE app for all their activities; they rarely use web browsers.
Preflight checklist
Ory Network Project
No response
Describe your problem
Line LIFF
, which do not implement OIDC. I attempt to map the UID provided by theLine Liff SDK
to a Kratos identity. Although I've tried usingpasswordless.code
, the documentation appears outdated, and I encounter errors when enabling it.kratos.yml
identity.schema.json
Session Arbitrary Metadata Fields: It's essential to include fields specific to each session, such as the business unit or role associated with the session. However, managing these through relations in KETO requires significant effort in terms of cleanup for revoked, timed-out, or unused sessions.
Email Template Customization: The current level of customization for email templates is insufficient. For instance, when users register from different platforms like Bitbucket or Jira, I need the email templates to reflect the branding of the respective platform. However, managing this customization for various scenarios becomes cumbersome.
Describe your ideal solution
.To
,.Identity
, in create those flow optionsWorkarounds or alternatives
Current workarounds involve manual interventions, such as directly generating and inserting tokens into the database or using external key-value stores for metadata storage. Additionally.
Version
v1.0
Additional Context
No response