Feature Request - Guest/ReadOnly Account

[futura]

I did some cursory searches in the forums and couldn't find anyone else posting about this, but if it is has been requested/discussed before, please post the link.

I just purchased Vault for my (small: <5) development team. I'm at 4 users at the moment.

What I think is really cool is the (unsupported) RSS feed feature. However, as Eric pointed out in his blog post about it, that it requires one to put their username/pass into the URL.

Although implementing basic-auth on the rss2.aspx page would be ideal, for asp.net reasons I understand why that isn't necessarily an option here.

As for another option, it'd be cool to have a "Guest" type of account that does not adversely affect the licenses that could be setup as "read-only". In our small environment, security to a repository, etc. is good - but not required. So having global read-only access to things is acceptable because the biggest thing we need to protect against is certain people making modifications to code that doesn't need to be modified. Viewing it isn't necessarily an issue.

There are other applications to this as well for general repository access, but would work really well on the RSS feed feature.

Thanks,
Aaron

[lbauer]

Everyone who accesses Vault needs a license.

You could use your extra license to create a Guest account that had read-only access, if you turn on security for your Repository.

Then unnamed users could log in as Guest and take a peek at the source code.

[futura]

I understand that I could use my last slot to create the read-only guest account. However, I guess I was specifically thinking that it would be flexible if the product didn't cause that to happen.

Guest access is access to the product - I completely understand that from a licensing standpoint. Although I would say that having read-only access is next to no privileges isn't really using the product and is that worth losing a license slot for?

I completely understand, I just thought it could be a flexible feature for smaller environments.

Thanks for your reply, Aaron