Skip to content

General

General

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

86 results found

  1. like lovable+supabase

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. With growing tensions between the US and EU, European enterprise customers' concerns about data privacy are growing.

    In order to continue using Firebase as a core technology stack, customers are demanding additional assurances, such as CMEK or even externally managed encryption keys (like those managed by Thales or T-Systems).

    Often, those enterprise customers are major revenue drivers, making service providers dependent on Firebase question their choice of Firebase as their infrastructure.

    This can be a primary driver for adoption away from Firebase services as a whole to different services or platforms.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. We are using Firebase authentication for sending OTP's to users.
    Currently the OTP message contains the text: "Your OTP is 123456. Sent via com.myapp.firebase.com"
    Our team would like to remove or customize the domain reference for branding and user trust reasons. We feel this part can confuse users or make the message looks suspicious. Please allow developers to either:
    Remove the domain
    Replace it with custom branding
    This change will help improve use trust and experience in production apps.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Allow setting the experation time for refresh tokens. This is important in environments where security is paramount and would allow for user session to automatically expire after a given amount of time.

    Currently this can be done with some work via the admin API, but seems to make much more sense as a setting, in line with other idPs such as Cognito1 and Auth02

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Hello everyone,

    currently not all email templates can be changed. For example, when activating multifactor authentication, you have to be satisfied with the ugly automatically generated email from firebase. It would probably be an easy to implement development if you could deactivate the automatic sending of the email template with a checkbox. Then you could implement your own email dispatch. Please provide a way to disable the automatic sending of email templates.

    Thank you and best regards

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. The way that Firebase helps developers quickly setup OAuth providers is amazing, but it would be really helpful if there were more providers to choose from. I'm sure you could do it if you set things up yourself, but making it easier to use services like LinkedIn would be really helpful.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. full support for KMM android, web, ios and desktop.
    What is the point of not supporting all of these?

    we build the best car but you can only use one wheel. Not a great theory for adoption.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. This is a problem I have encountered while using Firebase with Swift. I want to be able to prompt the user to sign up if they do not have an account. However, the error returned from Auth.auth().signIn(withEmail, password) is the same if the user enters the wrong password or an email the doesn't exist. If the errors were different I would be able to show the sign up prompt only if that specific error is thrown.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. When leveraging firebase for OIDC based authentication, there is data loss in mapping of standard user profile attributes between IdP and app such as given name, family name and other attributes as specified in the standard specifications[1]. Firebase auth must implement the specification properly and ensure against data loss.

    [1] https://www.iana.org/assignments/jwt/jwt.xhtml

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. I want to be able to perform an OTP verification for logging into my application using firebase.
    I want this feature to follow the following user journey:
    - Request OTP for login.
    - OTP sent to my email.
    - I type in the OTP for verification.
    - Authentication and access granted.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. The issue I am encountering is quite unusual. It arises whenever we try to access storage, even though I am using App Check and Firebase authentication is not required. Our App Check setup appears to be functioning correctly, and we can fetch data without any problems. However, these errors still appear in the console. This issue is occurring only in the Android, while the iOS works fine.

    Console error:
    error getting token java.util.concurrent.ExecutionException: com.google.firebase.internal.api.FirebaseNoSignedInUserException: Please sign in before trying to get a token.

    0 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Currently there is no way to customize the email sent to users who authenticate via email (deep ?) link. I understand / accept the rational for this.

    For Firebase projects with multiple Apps, this leads to all authentication emails having a single title (and link) based on the "public-facing name" set in "Project settings". It would be good to have an option to use the "app nickname" used for each of the Apps within the project to form the basis for the email title + link text. This would give users more confidence that they've received a valid login email…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Authentication  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Would be a HUGE cost saver given the increased pricing of SMS multi factor authentication.

    If Firebase knows the phone number / email via another project, offer the app user to share their phone number with this app and skip costly SMS verification.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. The firebase-ui https://github.com/firebase/firebaseui-web seems to no longer be supported. It currently doesn't support the latest firebase versions: https://github.com/firebase/firebaseui-web/issues/1107

    56 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. According to
    https://firebase.google.com/docs/auth/web/email-link-auth#default-email
    and
    https://github.com/firebase/firebase-js-sdk/issues/2574
    The email sign in template contains a timestamp in the email title and body, so email are not collapsed into a sigle thread.

    I believe the current date time format, such as 2024 November 11 13:33 UTC is not user friendly, and should be replaced with a more readable format, such as Nov. 11, 2024, 11:33.

    The mail language is already based on the language set in the Firebase Authentication -> Template language section, so the formatting can be done based on the same setting, or a new option can be added in the Firebase…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Application that is intended only for students of one university and I want to restrict creating of new accounts only to students of the specific university. There is a workaround of setting rules for data access in database, but I want to disallow other people to create a new account. Cleaner solution.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Dear Firebase Support Team,

    I hope this message finds you well. I am reaching out to share a suggestion that I believe could greatly benefit Firebase Authentication and developers working on more complex applications.

    Currently, Firebase Authentication provides excellent flexibility with signInWithPhoneNumber and createUserWithEmailAndPassword, allowing projects to authenticate users using either a phone number or an email/password combination. However, in certain projects, both the phone number and email/password are essential to meet higher security standards and user profile requirements.

    In these cases, having an integrated authentication flow that combines signInWithPhoneNumber and createUserWithEmailAndPassword within a single, cohesive process would be highly…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. When using Sign in with Apple, a default button that says "Continue to the app" appears. Please allow some kind of developer choice to either style this button, get rid of it completely (this youtube video https://www.youtube.com/watch?v=rJi_Mo-SdW0 seems to suggest the redirect/popup is not even needed at all and the sign in can happen on the actual login page with only a native apple modal, perhaps the Firebase SDK could allow this kind of flow), or another solution that does not involve an unstyleable button.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Food delivery services usually need to know the phone number of their customers, to guarantee that the deliveries will be smooth.

    So, a food delivery app would probably prefer authenticating users by phone number rather than by email address.

    Phone auth on its own isn’t particularly secure, though, so it would be nice to allow users to optionally add email authentication as a second factor.

    As of right now, phone auth doesn’t support MFA, though, which means that a food delivery app might want to force users to use email and phone 2FA right away, which might seem intrusive to…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5
  • Don't see your idea?