Configure the ASP.NET MVC 5 web application to use an external database for user authentication

When a new ASP.NET web application is created with the authentication set to Individual User Accounts, it automatically creates an SQL Express internal database in the App_Data directory of the application when you register the first user. To create the ASP.NET web application with user authentication see Create an ASP.NET Web Application with user authentication

This is sufficient for a small, proof of concept web application, but enterprise-grade applications should use a secure, backed up database.

To connect an ASP.NET MVC web application to an external database

  1. Create a new database in the database server
  2. Create a user and add it to the database as db_owner
    DECLARE @user_name varchar(50)
    SET @user_name = 'MY_USER_NAME'
    -- Create the user account
    -- Add the user to the database 
    USE MY_DATABASE_NAME; EXEC sp_grantdbaccess @user_name; EXEC sp_addrolemember @rolename = 'db_owner', @membername = @user_name;
  3. Replace the connection string in the Web.config file
        <add name="DefaultConnection"
            connectionString="Data Source=MY_SQL_SERVER_NAME;Initial Catalog=MY_DATABASE_NAME;user id=MY_USER_NAME;password=MY_PASSWORD"
            providerName="System.Data.SqlClient" />

There are two way to generate the user authentication tables

Use the new web application to automatically generate the tables

  1. Run the ASP.NET MVC 5 web application
  2. Select Register in the menu of the web application and register a user
  3. The application will automatically generate the user authentication tables in the database

Generate an SQL script to create the database

Delete the existing database

Only delete the existing database if you have no important data or configuration changes in the existing database!

The script generator checks the database for existing tables, so if you have used the web application to automatically create the tables, delete the database, so the generated script will contain all necessary steps to create the entire database.

  1. Close the tab in Microsoft SQL Server Management Studio that you used to connect to the new database to close the open connection to it
  2. Open a new tab in Microsoft SQL Server Management Studio and execute

Configure the web application for Code First development.

  1. In the Tools menu of Visual Studio select NuGet Package Manager, Package Manager Console
  2. At the bottom of the screen, the Package Manager Console window opens
  3. In the Package Manager Console execute
    Enable-Migrations –EnableAutomaticMigrations

    PM> Enable-Migrations –EnableAutomaticMigrations
    Checking if the context targets an existing database…
    Code First Migrations enabled for project USC_SocialMediaWebApp.</blockquote

  4. The command generates the Configuration.cs file in the Migrations folder of your solution.

Generate the code to update the database

  1. In the Package Manager Console execute
    Add-Migration Init

    PM> Add-Migration Init
    Scaffolding migration ‘Init’.
    The Designer Code for this migration file includes a snapshot of your current Code First model. This snapshot is used to calculate the changes to your model when you scaffold the next migration. If you make additional changes to your model that you want to include in this migration, then you can re-scaffold it by running ‘Add-Migration Init’ again.

  2. The command generates the necessary code to create the database tables

If you make changes to your models or the seeding script, execute the “Add-Migration Init” command again in the  Package Manager Console.

Create the database

The steps above generated the necessary code to create the database. To create the database

    1. For the script to be able to create the database, temporarily replace the “db_owner” user with a username and password of a “dbo” user in the database server. Otherwise, we may get

      System.Data.SqlClient.SqlException (0x80131904): CREATE DATABASE permission denied in database ‘master’

      Error Number:262,State:1,Class:14
      CREATE DATABASE permission denied in database ‘master’.

    2. In the Package Manager Console execute
      Update-Database -Verbose

      The -Verbose option displays the executed SQL commands during the database creation. You can save them to create the production database by executing it.

      PM> Update-Database
      Specify the ‘-Verbose’ flag to view the SQL statements being applied to the target database.
      Applying explicit migrations: [201802120745059_Init].
      Applying explicit migration: 201802120745059_Init.
      Running Seed method.

    3. Change the username and password back to the “db_owner” user credentials in the Web.config file of the web application.
    4. Execute this SQL statement in Microsoft SQL Management Studio to add the “db_owner” user to the database
      DECLARE @user_name varchar(50)
      SET @user_name = 'MY_USER_NAME'
      -- Add the user to the database 
      USE MY_DATABASE_NAME; EXEC sp_grantdbaccess @user_name; EXEC sp_addrolemember @rolename = 'db_owner', @membername = @user_name;

Flashing Side Marker Lamps

In the US it is not required to make the turn signals visible from the side of the vehicle. Many cars sold in the US have their front turn signals positioned between the headlights, so those are usually not visible from the side. If another car is next to yours, the other driver cannot see your rear turn signals, and because there are no front turn signals on the corner of your vehicle, they cannot see the font signals either. You can mount additional turn signals on the side of your car, but most of the time you need to drill holes into the body of the car, that can open the door for early corrosion of your vehicle.

If your car uses conventional light bulbs for the turn signals and the side markers, it is easy to make the side markers flash too.

The idea came from Daniel Stern at Read the “Crossfeed method” section for the explanation how it works.

Flashing side marker with lights off

Flashing side marker with lights on

The Honda CR-V has plenty of room under the hood to make this modification easy.

  1. Find the side marker and turn signal lights
  2. Disconnect the turn signal connector from the back of the turn signal bulb
  3. Remove the black electrical tape at the junction where the turn signal wires go down to the bulb
  4. Cut the black ground wire with one (1) silver dot leading to the side marker closer to the battery end
  5. Connect the side marker end of the black grounding wire with one (1) silver dot to the wire that goes down to the turn signal. Daniel Stern recommends the Posi-Tap connector to make this connection. The advantage is that you don’t have to cut the turn signal wire, just tap into it. (
  6. I did not have any tapping hardware, so I cut the turn signal wires and used crimp connectors to connect the ground of the side marker bulb to the hot wire of the turn signal.
  7. Temporarily reconnect the turn signal wire to the bulb to test the connection. When the lights are off, the side marker should flash in sync with the turn signal. When the lights are on, the side marker should light up, and when the turn signals operate it should flash too, but in opposite phase. (See videos above)
  8. Disconnect the turn signal wire again to make more room to work, and use a good quality black electrical tape to seal the junctions
  9. Reconnect the turn signal wire.

Create a Splunk HTTP Event Collector token

To receive HTTP post messages in Splunk, we need to create a Splunk HTTP Collector token.

To create an index for this token see Create a Splunk index

  1. In the Settings menu select Data Inputs
  2. Select the HTTP Event Collector link
  3. Click the New Token button
  4. Enter a name and description for the token and click the Next button
  5. Select the index to store the events in, set it as the default index, and click the Review button
  6. Click the Submit button to create the token
  7. The confirmation screen shows the token. You will be able to see it again on the token list page. Click the Start Searching button to see the search statement to see the events collected by this token.
  8. You can always search for the events with
    source="http:MY_INPUT" (index="MY_INDEX")

  9. The HTTP Event Collector token list shows the token.



464 km. Útvonal: Santa Monica (10) – (5) Pyramid Lake (99) – Visalia –Fresno – (41) –Oakhurst -(49) –Mariposa

41 C fok árnyékban. Séta a városban, kedves kis város, főleg a “Szalon”. Éjszaka rettenetes meleg és rettenetes zajos légkondi, füldugóval alszunk.


2. nap. Yosemite Nemzeti Park

View Larger Map

70 km. Útvonal: Mariposa ( reggel 30 C fok), (140) – A park bejárata után megálltunk, szép rálátás volt a Merced folyóra, sokan fürödtek, a folyón sok kis zuhogó volt. Bementünk a Visitor Centerbe, térkép, stb.

Parkolás, megkerestük a Shutle bust, elmentünk a „8” –as pontig, megkerestük a Valley floor tours indulási helyét. 2 órás utazás megállásokkal a legszebb pontokon, így körbejártuk a park leglátványosabb helyeit. El Capitan-Bridalveil fall-Tunnel View , (itt csodálatos panoráma van a hegyekre)-Half Dome- Campingek-vissza a 8-as pontra.

Visszaérkezés és ebéd után   20 perces sétával elmentünk a  Yosemite fall-hoz.

A Parkban nem volt kibiírhatatlan meleg, csak a napon volt  melegebb.

A Wawona road-on (41), majd a Glacier Point Roadon, rengeteg kanyarral , szerpentineken elmentünk a Glacier Point-hoz. Innen belátható az egész Yosemite Nemzeti Park felülről a camping a sátrakkal együtt, a Half Dome és a vízesések. Nagyon szép a kilátás.Medvével nem találkoztunk szerencsére.Itt sokan várták a naplementét.

Vissza indultunk Mariposába (41)-Oakhurst-  (49).Legalább 1OO kannyar volt a 41-es uton.Éjjel tudtunk aludni, mert a szoba végre lehült és kikapcsoltuk a szörnyeteget.(Kint továbbra is hőség 38 C fok)