Setting Up IntelliJ Run/Debug Configurations

By -

 

IntelliJ is a powerful integrated development environment that supports many languages and supports multiple module applications. When starting out, the configuration page may seem daunting because configurations may not auto populate. In this example we will be setting up the build for a Vue application; but the process is the same for any JavaScript framework using a node express server.


To get it started, click the + button to add a new configuration. From the list select the framework you are using for your application. Depending on your selection, some defaults will be provided. For example, when npm is selected it will search for a package.json in your directory and set the command.


This is the basics to get your applications started, but we can take this a little bit further. In a typical team environment, the package.json is getting updated as team members are adding dependencies for the code. We can use the Before launch section to make sure everything is updated before it runs.


The most basic use of this section is to add a Run npm script to do npm update so your package.json tracks with the remote version and is up to date every time it runs.



But let’s say you are developing a REST application; you can use the Run another configuration option to point to the configuration for that application. This is especially useful when developing applications that rely on multiple backend services to run.


Popular posts from this blog

ASP.NET Identity Remember Me

By -
ASP.NET Identity comes with a built-in Remember Me feature on the Login form, it's supposed to keep a user logged in (via an authentication cookie) for a predetermined period of time set via your code settings. However it sometimes might not work as expected and users will have to frequently log in which will cause quite a bit of frustration. Your first reaction is to modify your code then test / rinse / repeat and possibly still see the same unsuccessful results ... did you also check your website's IIS settings? Code Settings Let's first take a look at the Code configuration settings. If you create a new default MVC 5.x application in Visual Studio (with Authentication set to  Individual User Accounts ) the following code is generated (in  /App_Start/Startup.Auth.cs ): app.UseCookieAuthentication(new CookieAuthenticationOptions { AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie, LoginPath = new PathString("/Account/Login"), Provi
Read more

IIS Express Client Certificates

By -
We recently had to investigate how to  CAC -enable a web application, one of the challenges was setting up a proper development environment to prototype & test code changes before deploying to other environments. STEP 1  - You need to have a client certificate installed on your development machine. Assuming you don't have a readily available CAC or Smart Card, you can either  create a self-signed certificate  OR for this example we just used a  corporate outlook email client certificate (used to sign & encrypt emails).   Note : The certificate should be available in your web browser. For IE go to  Internet Options > Content > Certificates  to view all your certificates. In Chrome, go to  Settings > Show advanced settings > HTTPS/SSL > Manage certificates . STEP 2  - Using Visual Studio, create a default ASP.NET MVC 5 web application. STEP 3  - Enable SSL for your project. In Visual Studio, hit  F4  to open Project Properties and set   SSL Enabled   to   T
Read more

ASP.NET MVC - How to enable/disable CaC/Client Certificate authentication per area or route.

By -
Image
Use Case Typically, when you enable CaC/Client Certificates on a web app you enable it for the entire app. But what if you wanted to disable it for certain sections of the site. For example, an API controller, or a specific Area that hosts pages that can be publicly viewed. Luckily, it's very easy to make this happen. I'll walk through an example that requires CaC authentication for the base app but does not require it to make requests on an API controller, which will use leverage the HTTP Authentication header for auth.  1. Modify the web.config To require client certs for the base app, add this snippet inside the <system.webServer> tag. <!-- Access for the Base App --> <security> <access sslFlags="Ssl, SslNegotiateCert, SslRequireCert" /> </security> Now we can selectively disable client certs for specific sections of the app. In this case, I am disabling it for all routes starting with /api/v1 .
Read more