There is a post from Mar 2023 titled “Include website name in alias created with simplelogin” Include website name in alias created with simplelogin
I’m having the same issue with the desktop app, brave browser ext, and ios app when creating a new entry, no website prefix is generated with simplelogin (inside bitwarden). If I edit an existing entry and regenerate a simplelogin username same thing. However, if I EDIT an existing entry and regenerate a new simplelogin email username in the ios app it will include the website name in the created alias. Is it possible to do this in the browser and/or the desktop app as well? Is it possible to do this with a brand new entry on any platform?
@Billeye Hi!
I think this should be resolved with the current or next releases for the browser extensions, desktop apps, …:
main
← tools/PM-16171/Simplelogin-alias-generation-issue
opened 04:10AM - 23 Jan 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-16171
## 📔 Object… ive
This PR addresses the issue where the Simplelogin alias generator creates random words instead of including the current website's domain name. The new implementation ensures that aliases are generated based on the active website domain and updates the Simplelogin alias note appropriately.
The alias should be generated in the format [email protected] , where website is derived from the current browser tab's domain.
The alias note in Simplelogin should include:
Website: www.website.com. Generated by Bitwarden.
## 📸 Screenshots
https://github.com/user-attachments/assets/e07a1859-ccae-416d-9d6f-f6244dcd5aa9
https://github.com/user-attachments/assets/e00e8f60-9904-41b8-82cc-527f1907c02f
This PR also refines the error displayed when the service returns a 403. This error can be seen by generating more email addresses in FirefoxRelay than your subscription supports. (With a free subscription, that's 5 addresses.)
<img width="390" alt="image" src="https://github.com/user-attachments/assets/de0a799c-fcf3-4710-a259-1dc8fa5aab4a" />
## ⏰ Reminders before review
- Contributor guidelines followed
- All formatters and local linters executed and passed
- Written new unit and / or integration tests where applicable
- Protected functional changes with optionality (feature flags)
- Used internationalization (i18n) for all UI strings
- CI builds passed
- Communicated to DevOps any deployment requirements
- Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team
## 🦮 Reviewer guidelines
- 👍 (`:+1:`) or similar for great changes
- 📝 (`:memo:`) or ℹ️ (`:information_source:`) for notes or general info
- ❓ (`:question:`) for questions
- 🤔 (`:thinking:`) or 💭 (`:thought_balloon:`) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
- 🎨 (`:art:`) for suggestions / improvements
- ❌ (`:x:`) or ⚠️ (`:warning:`) for more significant problems or concerns needing attention
- 🌱 (`:seedling:`) or ♻️ (`:recycle:`) for future improvements or indications of technical debt
- ⛏ (`:pick:`) for minor or nitpick changes
I’m not so sure if the same is true with the iOS app, so it might be an idea, to report it as a “New issue” there.
1 Like