When we use DSN inside our code-base and git commit the changes, anyone can see the DSN, who ever has access to the repository. So my question, Do we need to keep the DSN private in some kind of environment variable or it can be just pasted as a hard-coded value inside the code-base.

You can create just a new DSN and delete old ones. You can find this in your project settings -> Client Keys. Recommending storing the DSN somewhere private would be conflicting messaging from our side. Let’s imagine you use @sentry/browser on your website, it’s impossible to hide the DSN in javas…

DSN private/public

SDKs

mittalyashu March 25, 2019, 11:43am 4

So, why don’t you recommend to the users to store their DSN as a variable key or keep it somewhere private. (just curious to ask)

Topic		Replies	Views
Should DSNs be kept private? SDKs	1	3251	April 16, 2019
RSN Key regenerating	1	1711	March 11, 2020
React Native DSN: public or private?	1	1373	April 19, 2017
How does Sentry prevent spammers?	2	5982	November 22, 2019
Raven.js: configure() lets DSN be exposed in page source?	1	1850	July 24, 2017

DSN private/public

Related topics