HelloZeroNet / HelloZeroNet/ZeroNet

Changing ID authority/provider name may disable user to select user ID?

Open
#1,272 2 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
18.8k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

### Step 1: Please describe your environment

* ZeroNet version: 0.6.1 rev3234
* Operating system: Win. 10
* Web browser: Firefox
* Tor status: available
* Opened port: yes

### Step 2: Describe the problem:

When i as a zite (zerotalk clone) admin edited ID providers names, example kaffie.bit to id.kaffie.bit and nanasi to nanasi.bit in websiteaddress/js/all.js and websiteaddress/content.json files, then the users who registered on site using old ID provider names (kaffie.bit, nanasi) no longer can login on my zite / switch their identity. I mean when switching identity (ID providers) as a zite user, then their old login names (example: myusername@nanasi) are shown in menu, but can not be clicked because such identity provider name no longer exist (nanasi.bit is new one set by zite admin), in menu i am offered to register new identity on same provider, but on identity provider zite i am already logged in and i am not interested to register new ID, because i will loose track of comments on my old ID posts if i am right?
-> So if zite admin modify ID provider name/url, like me, all users loose option to switch ID provider to one that i edited (if i am correct).

Why i edited ID providers names? Because when i used nanasi (which is suggested at many zites), the result was that when some user clicked to register new ID on it, i think (may be wrong) it redirected him to non existing page http://127.0.0.1:43110/nanasi
Similar for kaffie.bit, where the page does not directly contain form to register new ID so i wanted to use provider name as id.kafie.bit where he can directly register id.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with websiteaddress/js/all.js and websiteaddress/content.json, then trace the identity-switching flow for users whose provider name was changed. Reproduce the old-provider case and determine how provider renames are represented. Done means existing identities remain selectable after an administrator changes the provider name, without forcing users to register a replacement identity.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication, web-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.