---
description: Traditional web app that runs on the server
---

# Regular Web App

[![LLM | View as markdown](https://img.shields.io/badge/LLM-View%20as%20markdown-blue)](https://raw.githubusercontent.com/authgear/docs/refs/heads/main/get-started/regular-web-app/README.md)

If your application is a traditional web app running on a server, for example, **Java EE, Express, PHP, GO, Laravel, or** [**ASP.NET**](http://asp.net/) **Core MVC,** you can leverage the OpenID Connect (OIDC) protocol to authenticate users via Authgear. A wide range of plug-and-play libraries can be found that simplify the integration process. These libraries handle crucial tasks such as authentication requests, session management, and redirecting users back to your application seamlessly.

{% content-ref url="express.md" %}
[express.md](express.md)
{% endcontent-ref %}

{% content-ref url="next.js.md" %}
[next.js.md](next.js.md)
{% endcontent-ref %}

{% content-ref url="python-flask-app.md" %}
[python-flask-app.md](python-flask-app.md)
{% endcontent-ref %}

{% content-ref url="java-spring-boot.md" %}
[java-spring-boot.md](java-spring-boot.md)
{% endcontent-ref %}

{% content-ref url="asp.net-core-mvc.md" %}
[asp.net-core-mvc.md](asp.net-core-mvc.md)
{% endcontent-ref %}

{% content-ref url="laravel.md" %}
[laravel.md](laravel.md)
{% endcontent-ref %}

{% content-ref url="php.md" %}
[php.md](php.md)
{% endcontent-ref %}