Answers

  1. In the App_Start/Startup.Auth.cs class.
  2. Put the setting in Web.config and use ConfigurationManager to retrieve the settings at runtime.
  3. If we are working with sensitive information such as names, addresses, and bank account details, we should use an SSL encryption to protect the user and ourselves from malicious third parties interested in stealing our data.
  4. There is a performance overhead using SSL, so if our content is not sensitive, then we get no benefit from encrypting it, and we degrade the performance.
  5. A wildcard certificate.
  6. Add a redirect to the Web.config file. Doing this in a transform allows us to apply this to release configs, so we can debug against the HTTP endpoint too.
  7. Organizational Accounts.
  8. Enable Organizational Authentication ...

Get Learning Microsoft Azure now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.