From 6c65e97e49d1d56380aa7d71abb0394b08ff60ca Mon Sep 17 00:00:00 2001 From: Owen Jacobson Date: Sun, 24 Aug 2025 16:00:45 -0400 Subject: Return an identity, rather than the parts of an identity, when validating an identity token. This is a small refactoring that's been possible for a while, and we only just noticed. --- src/user/handlers/password/test.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/user/handlers/password') diff --git a/src/user/handlers/password/test.rs b/src/user/handlers/password/test.rs index ffa12f3..c0f789b 100644 --- a/src/user/handlers/password/test.rs +++ b/src/user/handlers/password/test.rs @@ -38,12 +38,12 @@ async fn password_change() { let new_secret = new_cookie .secret() .expect("we should have a secret after changing our password"); - let (_, login) = app + let new_identity = app .tokens() .validate(&new_secret, &fixtures::now()) .await .expect("the newly-issued secret should be valid"); - assert_eq!(identity.user, login); + assert_eq!(identity.user, new_identity.user); // Verify that our original token is no longer valid let validate_err = app @@ -72,10 +72,10 @@ async fn password_change() { .login(&name, &to, &fixtures::now()) .await .expect("logging in with the new password should succeed"); - let (_, login) = app + let identity = app .tokens() .validate(&secret, &fixtures::now()) .await .expect("validating a newly-issued token secret succeeds"); - assert_eq!(identity.user, login); + assert_eq!(name, identity.user.name); } -- cgit v1.2.3