[GH-ISSUE #426] question - how do we change the name given to the token in authy? #250

New issue

Closed

opened 2026-03-03 01:27:14 +03:00 by kerem · 15 comments

kerem commented 2026-03-03 01:27:14 +03:00

Owner

Copy link

Originally created by @pdarcos on GitHub (Mar 6, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/426

When I use authy with 2FA it shows the name of the account as Bitwarden.

Where is this located in the code so I can change it?

Thanks

Originally created by @pdarcos on GitHub (Mar 6, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/426 When I use authy with 2FA it shows the name of the account as Bitwarden. Where is this located in the code so I can change it? Thanks

kerem closed this issue 2026-03-03 01:27:14 +03:00

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 6, 2019):

It's hardcoded into the web vault, here. As it is we can't do much about it.

<!-- gh-comment-id:470315202 --> @dani-garcia commented on GitHub (Mar 6, 2019): It's hardcoded into the web vault, [here](https://github.com/bitwarden/web/blob/2b6ce14a32e2aadd54cc6d1800f2dec37f151d84/src/app/settings/two-factor-authenticator.component.ts#L85). As it is we can't do much about it.

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 7, 2019):

Hmm, couldn't we just change that line and on the next where it states "&issuer=Bitwarden"?

Or am I forgetting something?

<!-- gh-comment-id:470531975 --> @pdarcos commented on GitHub (Mar 7, 2019): Hmm, couldn't we just change that line and on the next where it states "&issuer=Bitwarden"? Or am I forgetting something?

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Mar 7, 2019):

You are forgetting, that this file is statically served, so any change there would also be static. So it would have to be build-time change.

<!-- gh-comment-id:470535762 --> @mprasil commented on GitHub (Mar 7, 2019): You are forgetting, that this file is statically served, so any change there would also be static. So it would have to be build-time change.

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 7, 2019):

Got it. But if we compile the web-vault ourselves with those changes it should work, right?

<!-- gh-comment-id:470551070 --> @pdarcos commented on GitHub (Mar 7, 2019): Got it. But if we compile the web-vault ourselves with those changes it should work, right?

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Mar 7, 2019):

Yes it will work.

<!-- gh-comment-id:470558675 --> @mprasil commented on GitHub (Mar 7, 2019): Yes it will work.

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 7, 2019):

OK, I'm going to venture into this to see if it works.

I git cloned https://github.com/bitwarden/web.git

Then I started following your instructions here https://github.com/dani-garcia/bitwarden_rs/wiki/Building-binary

I cd into web folder and then I downloaded your v2.8.0.patch and tried to apply it as instructed in the wiki

git apply v2.8.0.patch
error: unrecognized input

I must be missing something. Any ideas?

Thanks

<!-- gh-comment-id:470586894 --> @pdarcos commented on GitHub (Mar 7, 2019): OK, I'm going to venture into this to see if it works. I git cloned https://github.com/bitwarden/web.git Then I started following your instructions here https://github.com/dani-garcia/bitwarden_rs/wiki/Building-binary I cd into web folder and then I downloaded your v2.8.0.patch and tried to apply it as instructed in the wiki git apply v2.8.0.patch error: unrecognized input I must be missing something. Any ideas? Thanks

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 7, 2019):

Hmm, no idea why that could be happening. Can you chech that the downloaded patch file has the correct encoding and end of line characters? The copy of the patches I have locally are utf8 and use linux-style line feeds.

<!-- gh-comment-id:470590659 --> @dani-garcia commented on GitHub (Mar 7, 2019): Hmm, no idea why that could be happening. Can you chech that the downloaded patch file has the correct encoding and end of line characters? The copy of the patches I have locally are utf8 and use linux-style line feeds.

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Mar 7, 2019):

@pdarcos I think much easier approach would be to grab the pre-built Vault and just do your changes there.

<!-- gh-comment-id:470598168 --> @mprasil commented on GitHub (Mar 7, 2019): @pdarcos I think much easier approach would be to grab the [pre-built Vault](https://github.com/dani-garcia/bw_web_builds/releases/tag/v2.9.0-pre1) and just do your changes there.

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 7, 2019):

Thanks @mprasil
I'm going to try that approach since it is indeed much easier. But if it is already pre-built will I still be able to change the strings here ?

<!-- gh-comment-id:470601402 --> @pdarcos commented on GitHub (Mar 7, 2019): Thanks @mprasil I'm going to try that approach since it is indeed much easier. But if it is already pre-built will I still be able to change the strings [here](https://github.com/bitwarden/web/blob/2b6ce14a32e2aadd54cc6d1800f2dec37f151d84/src/app/settings/two-factor-authenticator.component.ts#L85) ?

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@mprasil commented on GitHub (Mar 7, 2019):

I think it should still be possible. At the end of the day it's just a bunch of javascript files and the string has to be somewhere there.

<!-- gh-comment-id:470602250 --> @mprasil commented on GitHub (Mar 7, 2019): I think it should still be possible. At the end of the day it's just a bunch of javascript files and the string has to be somewhere there.

kerem commented 2026-03-03 01:27:15 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 7, 2019):

Editing the already built vault is not the cleanest way, because the code is already minified, but for a small change like this it should be ok.

You'll need to edit the main.js file, I think. You can use search and replace for the &issuer=Bitwarden and otpauth://totp/Bitwarden: strings.

<!-- gh-comment-id:470602653 --> @dani-garcia commented on GitHub (Mar 7, 2019): Editing the already built vault is not the cleanest way, because the code is already minified, but for a small change like this it should be ok. You'll need to edit the `main.js` file, I think. You can use search and replace for the `&issuer=Bitwarden` and `otpauth://totp/Bitwarden:` strings.

kerem commented 2026-03-03 01:27:16 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 7, 2019):

Thanks guys. Found it in main.js indeed. Gonna change it and see how it works out

<!-- gh-comment-id:470604338 --> @pdarcos commented on GitHub (Mar 7, 2019): Thanks guys. Found it in main.js indeed. Gonna change it and see how it works out

kerem commented 2026-03-03 01:27:16 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 7, 2019):

To give feedback.

I ended up applying the patch (there was a typo when I copy/pasted the patch file that I fixed) and building the web-vault from scratch as per your wiki.

now it's built and working fine. The token no longer shows up as bitwarden :) Now if only I could figure out how to add an icon to the entry like cloudflare has (the original bitwarden also has no icon).

<!-- gh-comment-id:470634835 --> @pdarcos commented on GitHub (Mar 7, 2019): To give feedback. I ended up applying the patch (there was a typo when I copy/pasted the patch file that I fixed) and building the web-vault from scratch as per your wiki. now it's built and working fine. The token no longer shows up as bitwarden :) Now if only I could figure out how to add an icon to the entry like cloudflare has (the original bitwarden also has no icon).

kerem commented 2026-03-03 01:27:16 +03:00

Author

Owner

Copy link

@dani-garcia commented on GitHub (Mar 7, 2019):

That depends on the OTP client, in this case Authy. If they don't let you configure it manually, it means they jsust keep an internal list of some popular options, so there isn't much you can do.

<!-- gh-comment-id:470662097 --> @dani-garcia commented on GitHub (Mar 7, 2019): That depends on the OTP client, in this case Authy. If they don't let you configure it manually, it means they jsust keep an internal list of some popular options, so there isn't much you can do.

kerem commented 2026-03-03 01:27:16 +03:00

Author

Owner

Copy link

@pdarcos commented on GitHub (Mar 8, 2019):

Yeah, that makes total sense.
Thanks for the help guys.

Closing this now

<!-- gh-comment-id:471022941 --> @pdarcos commented on GitHub (Mar 8, 2019): Yeah, that makes total sense. Thanks for the help guys. Closing this now

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

revert-7033-patch-1

cached-config-operations

test_dylint

1.35.7

1.35.6

1.35.5

1.35.4

1.35.3

1.35.2

1.35.1

1.35.0

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels   

SSO

  

Third party

  

better for forum

  

bug

  

bug

  

documentation

  

duplicate

  

enhancement

  

future Vault

  

future Vault

  

future Vault

  

good first issue

  

help wanted

  

low priority

  

notes

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

troubleshooting

  

wontfix

No labels

SSO

Third party

better for forum

bug

bug

documentation

duplicate

enhancement

future Vault

future Vault

future Vault

good first issue

help wanted

low priority

notes

pull-request

question

troubleshooting

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/vaultwarden#250

No description provided.