You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in the Admin UI when editing a peer it is confusing how the interactions differ when dealing with the incoming vs outgoing auth token fields. The outgoing auth token is a required field and as such we always have the value sent to the frontend and include it in update requests. The incoming auth tokens are optional so we don't display them or include them on the frontend. When a user enters a value to update the field and they hit save they can still see the incoming value but if they refresh it disappears making them doubt whether the value actually saved or not. Also, not seeing the incoming auth tokens means people have to remember them or look them up if they want to make small changes like removing only one of the tokens.
This why we'd like to rather give users an editable drop down to see what incoming auth tokens they have currently and interact selectively with whichever they want to edit / remove / add.
The text was updated successfully, but these errors were encountered:
Currently in the Admin UI when editing a peer it is confusing how the interactions differ when dealing with the incoming vs outgoing auth token fields. The outgoing auth token is a required field and as such we always have the value sent to the frontend and include it in update requests. The incoming auth tokens are optional so we don't display them or include them on the frontend. When a user enters a value to update the field and they hit save they can still see the incoming value but if they refresh it disappears making them doubt whether the value actually saved or not. Also, not seeing the incoming auth tokens means people have to remember them or look them up if they want to make small changes like removing only one of the tokens.
This why we'd like to rather give users an editable drop down to see what incoming auth tokens they have currently and interact selectively with whichever they want to edit / remove / add.
The text was updated successfully, but these errors were encountered: