Skip to content

Authentication profile is not set correctlyΒ #842

@madsjk816

Description

@madsjk816

Checklist

  • I have looked into the README and have not found a suitable solution or answer.
  • I have looked into the documentation and have not found a suitable solution or answer.
  • I have searched the issues and have not found a suitable solution or answer.
  • I have upgraded to the latest version of this tool and the issue still persists.
  • I have searched the Auth0 Community forums and have not found a suitable solution or answer.
  • I agree to the terms within the Auth0 Code of Conduct.

Description

Since upgrading the auth0-deploy-cli tool from version 7.17.5 to the latest version 7.19.0 the 'Authentication Profile' setting is not being correctly deployed.

When deploying using version 7.17.5 the 'Authentication Profile' setting regarding identifier first is respected and set correctly, however, when deploying using version 7.19.0 the 'Authentication Profile' seems to be set to 'Identifier + password' which is quite unfortunate when you rely on password-less logins.

I've tried back and forth to slim down the tenant.yaml file to see what might cause the conflict, and it seems that the 'branding' part of it causes the issue to appear. If i remove the branding part of the .yaml file the 'Authentication Profile' is set to 'identifier-first' using both versions of the cli-tool

Expectation

When using the following setting in the tenant.yaml file

prompts:
  identifier_first: true

Identifier first is set as the authentication profile. If it is not possible due to conflicting settings would expect the tool to either throw a warning or an error.

Reproduction

A .yaml file with the following contents:

branding:
  logo_url: >-
    https://upload.wikimedia.org/wikipedia/commons/thumb/5/5b/Logo_de_Auth0.svg/800px-Logo_de_Auth0.svg.png?20211214133710
prompts:
  identifier_first: true
  universal_login_experience: new

run npm install -g [email protected]

'Identifier First' should be respected when using this version.

Next up:

run npm install -g [email protected]

The authentication profile is now set to 'Identifier + password'

Do the same procedure with the following contents in the tenant.yaml file instead:

prompts:
  identifier_first: true
  universal_login_experience: new

The 'identifier first' authentication profile is now set correctly using both versions of the cli-tool.

Deploy CLI version

7.19.0

Node version

16.14.2

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions