azureservicebus - Azure notification hubs shared access key expiry -



azureservicebus - Azure notification hubs shared access key expiry -

from azure portal, on configure tab notification hub able generate primary key , secondary key. understand these required gain programmatic access azure api - allowing client app create registrations , send messages.

could please explain:

why there 2 keys (primary , secondary)? keys generated ui expire , if how long live before expiry?

they don't expire. reason there 2 because it's recommended regenerate keys periodically security reasons. example, suppose application using primary key today. if regenerated primary key, application broken until update , resulting in downtime. instead, can alter application utilize secondary key little or no downtime. then, after application has been updated, can regenerate primary key. next month (or whatever schedule like), can repeat process, switching primary key , regenerating secondary key.

this not unique notification hubs. see primary , secondary keys in other services such storage , media services. thought same.

azure azureservicebus azure-notificationhub

Comments

Popular posts from this blog

php - Android app custom user registration and login with cookie using facebook sdk -

django - Access session in user model .save() -

php - .htaccess Multiple Rewrite Rules / Prioritizing -