# Reveal randomly generated password during installation

**URL:** <https://community.replicated.com/t/reveal-randomly-generated-password-during-installation/1218>\
**Category:** How do I?\
**Created:** [May 30, 2023, 8:01pm UTC](https://community.replicated.com/t/reveal-randomly-generated-password-during-installation/1218 "2023-05-30T20:01:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chbrosso](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/chbrosso/32/454_2.png) [@chbrosso](https://community.replicated.com/u/chbrosso)\
**Post date:** [May 30, 2023, 8:01pm UTC](https://community.replicated.com/t/reveal-randomly-generated-password-during-installation/1218/1 "2023-05-30T20:01:53Z")

</div>

Hello,

For the first login in our application, we generate a random password, currently stored in a secret. We provide in the documentation the kubectl command to be run for getting that password, but we’re looking for a more user-friendly way of doing it.

Is there any way of revealing that password after installation in the admin console? If not, can you advise a better user experience for this situation?

---

<div class="post-metadata">

**Author:** ![Alex\_Parker](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/alex_parker/32/777_2.png) [@Alex\_Parker](https://community.replicated.com/u/Alex_Parker)\
**Post date:** [June 28, 2023, 4:43pm UTC](https://community.replicated.com/t/reveal-randomly-generated-password-during-installation/1218/2 "2023-06-28T16:43:37Z")

</div>

Hey, Charles. I assume this password is a config option that is auto-generated.

If so, here are a couple options. In [KOTS v1.97.0](https://docs.replicated.com/release-notes/rn-app-manager#1970) we added an unmask button for passwords. This is only visible the first time the password is generated so that other people returning to the config page later cannot unmask and view the password. But during the initial installation, users could use the unmask button to view the password once. Then you could document how to find it later if people miss it.

The **View files** tab in the admin console is an alternative to using kubectl to get the password later. Config inputs are stored in the `upstream/userdata/config.yaml` file, so you could point users there to find their password too.