47 Matching Annotations
  1. May 2024
    1. Managing user accounts (registration, login, logout)

      Better: always log in with a server, unless you choose to migrate.

  2. May 2023
  3. Mar 2023
  4. Feb 2023
  5. Dec 2022
    1. HEADS UP!!! It is important to set the application/json as the Accept header.

      I was getting an invalid credential error and spent some time figuring out what the hell is going on.

  6. Sep 2022
  7. Aug 2022
  8. Jul 2022
  9. Apr 2022
  10. Jan 2022
  11. Oct 2021
      1. service account 自动mount
      2. service account 自动设置在pod的spec.serviceAccountName
      3. 1.6以上可以通过设置automountServiceAccountToken来disable自动mount的行为
      4. pod默认的service account是自己ns的default account
      5. 对于任意给定的serviceaccount 我们可以手动的给他创建token,方式是创建secret,在annotation中指定service-account,auto-controller会自动在这里更新token
      6. 无法更改已经创建的pod的serviceaccount
  12. Jul 2021
    1. Create an account or session

      This is the process of using social login. Google/FB does the authentication part. Once the token has been confirmed, create a new access_token and refresh_token for the user like a normal user who logged in via email/password.

  13. Jun 2021
    1. I do wonder a bit about the potential misuse/abuse of sending tickets as notifications to people who don't want them.

      Hopefully once the system is up and distributed it's relatively easy to ignore or block tickets from bad actors. Email spam is a similar model to this.

  14. Apr 2021
    1. All you need is an email address or phone number associated with an account and you will get a magic link or one-time password each time you want to log in. As soon as you click the link, you'll get redirected to the app and you'll already be logged in. After that, the magic link isn't valid so no one else can use it.
  15. Feb 2021
  16. May 2020
    1. code exchange with Auth0 and retrieve the user's id_token and access_token which will be stored in memory.

      Auth without backend

  17. Oct 2019
    1. When using account linking it is important to be aware that some limitations exist. First, only two accounts can participate in a link. If an attempt is made to link to an account which is already linked, the new link will replace the original link. It is also not possible to link two accounts associated with the same authentication provider. While a Facebook account may be linked with a Google account, for example, it is not possible to link two Google provider based accounts. An attempt to link accounts from the same provider will result in an exception containing a message which reads as follows: User has already been linked to the given provider. Account linking can only be performed at the point at which a new account is created. It is not possible, in other words, to link two pre-existing accounts. A workaround to this limitation is to delete one of the two accounts and then establish the link while re-creating the account

      so user cannot have 2 phone numbers or 2 emails :( :(

    1. recommend using Firebase when the API calls involve any user data and the API is intended to be used in flows where the user has an user interface
    1. Access control for GCP APIs encompasses authentication, authorization, and auditing. Authentication determines who you are, authorization determines what you can do, and auditing logs record what you did
  18. Sep 2019
  19. Sep 2018