FAQ
Jacob,

One question: the provider field will remain there, right? Just the uid
will have the format changed, but any other auth fields will be there,
right?

Douglas Correa

2015-08-27 14:12 GMT-03:00 Jacob Wenger <jacob@firebase.com>:
Hey Doug,

There is no schedule but the change is going to happen. You are correct
that there is no createUser() method, but when you call authWithOAuth*(),
you get back authData which has a uid in it. The format of that uid is
going to be switching to a UUID at some point in the future, so start
planning for it now. Ultimately this boils down to:

*The auth uid is meant as a unique identifier for the users in your
Firebase database, but you should not rely on the format of the uid in any
other way, as it is subject to change.*

Hope that helps,
Jacob
On Thu, Aug 27, 2015 at 9:58 AM, Doug Puchalski wrote:

Is there a schedule for OAuth?

I'm using emberfire, torii, and google for OAuth, so there's no explicit
call to createrUser(). Will the criteria operate differently?
On Thursday, August 6, 2015 at 11:57:20 AM UTC-7, Kato Richardson wrote:

Hi Folks! Hope you're all having a blast building apps on Firebase.


The format of the auth UIDs generated by Firebase will be changing on
Monday, August 17th. We’ll be changing from an incremental integer to a
UUID <https://en.wikipedia.org/wiki/Universally_unique_identifier>
(universally unique identifier).

This will affect the email/password and anonymous providers on the 17th,
and be extended to the OAuth providers (i.e. GitHub, Facebook, Twitter, and
Google) at some undetermined time in the future. If you’re manipulating or
parsing UIDs in any way, you’ll want to update your code and security rules
before the 17th.

When new users get created after this date, you may notice that, instead
of a string like <provider>:<number>, new accounts will have a UID
assigned that looks more like f47ac10b-58cc-4372-a567-0e02b2c3d479. You
should keep in mind that the contents of these strings are an
implementation detail and not intended to be meaningful. They are only
guaranteed to be unique and unchanging for a given user.

To reiterate, this will affect new UIDs created with createUser(), but
will not affect any of your existing users’ UIDs.

Below is a quick checklist to ensure your code won't be affected by this
change. If you have additional questions, reply here or reach out to
support@firebase.com.
auth.uid.contains() or auth.uid.replace()

If you are checking auth.uid begins with, contains, or doing any sort
of matching on the contents of this string, this will break. Particularly,
if you are doing a replace on ‘:’, this will almost certainly break.

Alternatives: Use auth.provider to obtain the provider name. If you
need to access the OAuth id (e.g. facebook ID) then you can
programmatically store this in your data when a user authenticates (e.g.
authData.facebook.id where authData is the return value from any
authWith*() call).
auth.uid.length

The length of new UID strings may be radically different than existing
UIDs created before this change. If you are checking to ensure the length
is greater than zero, that should continue to work, or could simply be
replaced by a boolean (e.g. “.read”: “auth.uid”).
auth.uid == x

If you are checking that the auth.uid matches another value stored in
the data, this should continue to work perfectly. Existing users’ UIDs will
not change and newly minted UIDs will have a different format, but still
work with this approach.
How to test this change

If you want to test your existing code against the new format, this gist
<https://gist.github.com/katowulf/d533678c9196f3d92ef4> illustrates how
to create a mock authentication token that will resemble the new UUID
strings.

Have a great day,

Kato

--
You received this message because you are subscribed to the Google Groups
"Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to firebase-talk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebase-talk/848c0c2d-c8d9-4ce8-aba0-b6edf0f8a020%40googlegroups.com
<https://groups.google.com/d/msgid/firebase-talk/848c0c2d-c8d9-4ce8-aba0-b6edf0f8a020%40googlegroups.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to firebase-talk@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/firebase-talk/CAGcMwsAe9XWYgJyjZJddoy43w1smV_soTX1v2JnodYkkqp%2B-6A%40mail.gmail.com
<https://groups.google.com/d/msgid/firebase-talk/CAGcMwsAe9XWYgJyjZJddoy43w1smV_soTX1v2JnodYkkqp%2B-6A%40mail.gmail.com?utm_medium=email&utm_source=footer>
.

For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-talk+unsubscribe@googlegroups.com.
To post to this group, send email to firebase-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/CAPUi1p3FMUKxA2RemVmDsdJ0_%3DS6AqtpcxTKiezLFXQ0mBouGA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

People

Translate

site design / logo © 2021 Grokbase