Validate Auth0 sign-in with a real account

Open
#806 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start with the Auth0 provider section of docs/src/crates/connect.md, then scaffold a new app with cargo rullst new and wire the provider through begin_login and finish_login. You will need a free Auth0 tenant with a redirect URI on http://localhost:3000, and keep credentials in a local .env. Done means you have signed in and out with a real account, checked the returned user fields, and posted the results (version, OS, tier, any exact errors) on the issue.

Written by the indexing model from the issue text.

Description

good first issue help wanted

rullst-connect's Auth0 provider is tested offline only (mock mode and parsed fixtures); nobody has signed in with a real Auth0 account yet.

Comment "I'll take this" before starting, so two people do not test the same thing. Use a free tier or trial where one exists, and delete what you created afterwards.

What to do

  1. Create an OAuth/OIDC application in Auth0's developer console (a free Auth0 tenant), with a redirect URI on http://localhost:3000 (or your test domain).
  2. In a new project (cargo install cargo-rullst --version =<latest 13.0 prerelease> --locked, then cargo rullst new), wire the Auth0 provider as the Connect guide shows, using begin_login/finish_login.
  3. Sign in with a real account; check the user fields that arrive (id, name, e-mail where the provider gives one) and that signing out and in again works.

Documentation: Connect guide

What to report (comment here)

  • Rullst version, operating system, and the plan or tier you used.
  • Whether each step worked, and the exact error text for anything that did not (remove secrets first).
  • Anything in the documentation that was wrong, missing or confusing.

Never paste API keys, client secrets, tokens or connection strings into the issue; keep them in your local .env. Bugs go in a bug report; fixes to the docs can be a pull request. A successful run is recorded in the documentation with its date, and the integration moves up on the website's "How far each integration has been tested" list.

Part of #801.

Dominant language
Rust
Stars
21
Forks
6
Avg merge
5h 35m
Merged PRs (30d)
246

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rullst/Rullst

All issues in Rullst/Rullst

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.