Explore Java Enterprise security, focusing on authentication, authorization, and information security. Gain insights into encoding, encryption, and hashing. Discover OAuth2 and OpenID Connect integration techniques.

new.tar.gz

taskOne

tasktwo

taskthree

formPF

oauth2

openid

ldap

hashing

JWTHello

JWKManager

JwtAuthCode

demo

Challenge 1

Challenge2

Challenge3

simple-hash

hash-with-salt

PBKD

Challenge2-Faizan

Challenge3-Faizan

This course covers authentication and authorization within web applications in Java Enterprise security. Security is a vast concept with many aspects. In particular, we'll focus on the security of applications and the data they contain, an area that is known as information security.

We will start by identifying our end users and dive deep into the differences between encoding, encryption, and hashing techniques. After that, we will learn to propagate information with microservices architecture.

By the end of this course, you'll have hands-on experience with the integration and configuration of OAuth2 and OpenID Connect into the Java application.

JakartaEE Security Workshop

For specification, the input field names in the submitted request need to be in the form of `j_xxx`. With the attribute, it would be `j_xxx`.

For specification, the input field names in the submitted request are not in the form of `j_xxx`. With the attribute, it would be `login.j_xxx`.

For the specification, the input field names in the submitted request need to be in the form of `j_xxx`. With the attribute, it would be `j_xxx.login`.

For the specification, the input field names in the submitted request need to be in the form of `j_xxx`. With the attribute, it would be `h:form.j_xxx`.

Why did we add the attribute `prependId="false"` to the `<h:form>` tag?

Why did we add the attribute <code>prependId=&quot;false&quot;</code> to the <code>&lt;h:form&gt;</code> tag?

We cannot indicate which role(s) is/are required to view an HTML or JSF page.

To keep the data hidden from all role(s).

Why do we need to provide the protected URLs in the `web.xml` when we didn't need them in the previous chapter's examples?

Why do we need to provide the protected URLs in the <code>web.xml</code> when we didn’t need them in the previous chapter’s examples?

Otherwise, the server will not recognize the login request and will deny it.

Otherwise, the password would be readable to anyone monitoring network traffic when the browser performs the request to the server.

Why should we use `HTTPS` for the login page?

Why should we use <code>HTTPS</code> for the login page?

Because the OpenID Connect specification defines how user information, such as names and roles, can be retrieved as data from an OAuth2 resource server.

Because they both use similar methods to save information.

Because the OpenID Connect specification defines how to authorize the user. 

Because OpenID Connect defines how user information is retrieved and authenticated. 

Why is OpenID Connect an extension of OAuth2?

Why is OpenID Connect an extension of OAuth2?

Test your understanding of what you’ve learned so far about authentication methods.

Before We Begin

Introduction

Concepts

Window Shopping

Authentication Methods

Standards

Authentication Data Stores

Secure Data Transfer

Quiz