Nico Sabena nicosabena

## Startup-for-OIDC-HS256.cs
using System;
using Microsoft.AspNetCore.Authentication.Cookies;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Http;
using Microsoft.Extensions.Configuration;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Logging;
using Microsoft.Extensions.Options;
using Microsoft.IdentityModel.Tokens;

## azure-ad-groups-with-client-credentials.js
// This rule will get the groups for users coming from Azure AD
// Auth0 already has the option to do that, but it (currently) won't work
// if the user is coming from a different directory than the directory
// where the app is registered (this can happen with multi-tenant apps).
// This is a variation that gets an access token for Azure AD using the
// client-credential grants instead of using the access token given to the user.
// It's useful if a new access token from Azure AD is not obtained every time the rule runs,
// or if WS-Federation is used instead of OIDC.
//
// After the rule runs, you will have the 'groups' property in the user

## cookie-check-hosted-login-page.html
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
  <title>Sign In with Auth0</title>
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
</head>
<body>
  <div id="nocookies" style="display:none">

## single-connection-hlp.html
<!DOCTYPE html>
<!--
  This hosted login page will go directly to a single upstream identity provider
  instead of showing Lock. It's a good choice for tenants that have only one
  connection enabled, or for individual applications with just one connection
  (in which case, the logic to decide to go directly to the idp needs to
  be changed, see below).
  It still keeps Lock if you do `prompt=login`, just in case.
-->

## delete_grants_after_password_change.js
async function (user, context, callback) {
  // this rule will run after a user changes their password and
  // delete, for the user, either:
  //   - all grants (for OIDC-Conformant usage)
  //   - all device credentials (for non OIDC-Conformant apps)
  // These actions will effectively invalidate all issued refresh tokens
  // on the next token request (be it an interactive login
  // or a refresh token flow).
  // It compares a user's last_password_rest property
  // against an "app_metadata.last_revoke" property used

## Lock-with-extra-button.html
<!--
This example how you can add an extra button to Lock to directly
force an authentication with an enterprise connection (instead of relying
on Lock's home realm discovery with the email domain).

Warning: This is provided "as-is". It relies on Lock's current DOM structure, which
might change in future versions without previous warning and break this solution.

If you want buttons for your enterprise connections, a better idea is to
use the "New" Universal Login experience instead, which provides these

## redirect-rule.js
function (user, context, callback) {

  // this rule requires the following configuration values:
  // CAPTCHA_SECRET: a 32 bytes string that will be the shared secret between
  //                 the rule and the webtask
  // AUTH0_DOMAIN: your auth0 domain (e.g. account.auth0.com)
  // CAPTCHA_REDIRECT: the URL for the webtask that will show and process CAPTCHA

  // Put a specific client ID if you dont want CAPTCHA for every client
  // if (context.clientID !== '[your client id]')

## embedded-lock-test.html
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML>
<HEAD>
    <meta name="viewport" content="width=device-width, initial-scale=1">
    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">
    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css" integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous">
    <TITLE>
        Hello World
    </TITLE>
    <style>

## smaller-header-hlp.html
<!DOCTYPE html>
<html>
<head>
  <meta charset="utf-8">
  <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
  <title>Sign In with Auth0</title>
  <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=0" />
  <style  type="text/css">

  /* completely hide the header

## Configure WS-Fed generated attributes.js
function (user, context, callback) {

  // only apply changes for the WS-Fed application
  if (context.clientName !== 'Your ws-fed application name') {
    return callback(null, user, context);
  }

  // exclude the upn claim creation (defaults to true)
  context.samlConfiguration.createUpnClaim = false;
	using System;
	using Microsoft.AspNetCore.Authentication.Cookies;
	using Microsoft.AspNetCore.Builder;
	using Microsoft.AspNetCore.Hosting;
	using Microsoft.AspNetCore.Http;
	using Microsoft.Extensions.Configuration;
	using Microsoft.Extensions.DependencyInjection;
	using Microsoft.Extensions.Logging;
	using Microsoft.Extensions.Options;
	using Microsoft.IdentityModel.Tokens;
	// This rule will get the groups for users coming from Azure AD
	// Auth0 already has the option to do that, but it (currently) won't work
	// if the user is coming from a different directory than the directory
	// where the app is registered (this can happen with multi-tenant apps).
	// This is a variation that gets an access token for Azure AD using the
	// client-credential grants instead of using the access token given to the user.
	// It's useful if a new access token from Azure AD is not obtained every time the rule runs,
	// or if WS-Federation is used instead of OIDC.
	//
	// After the rule runs, you will have the 'groups' property in the user
	<!DOCTYPE html>
	<!--
	This hosted login page will go directly to a single upstream identity provider
	instead of showing Lock. It's a good choice for tenants that have only one
	connection enabled, or for individual applications with just one connection
	(in which case, the logic to decide to go directly to the idp needs to
	be changed, see below).
	It still keeps Lock if you do `prompt=login`, just in case.
	-->
	async function (user, context, callback) {
	// this rule will run after a user changes their password and
	// delete, for the user, either:
	// - all grants (for OIDC-Conformant usage)
	// - all device credentials (for non OIDC-Conformant apps)
	// These actions will effectively invalidate all issued refresh tokens
	// on the next token request (be it an interactive login
	// or a refresh token flow).
	// It compares a user's last_password_rest property
	// against an "app_metadata.last_revoke" property used
	<!--
	This example how you can add an extra button to Lock to directly
	force an authentication with an enterprise connection (instead of relying
	on Lock's home realm discovery with the email domain).

	Warning: This is provided "as-is". It relies on Lock's current DOM structure, which
	might change in future versions without previous warning and break this solution.

	If you want buttons for your enterprise connections, a better idea is to
	use the "New" Universal Login experience instead, which provides these
	function (user, context, callback) {

	// this rule requires the following configuration values:
	// CAPTCHA_SECRET: a 32 bytes string that will be the shared secret between
	// the rule and the webtask
	// AUTH0_DOMAIN: your auth0 domain (e.g. account.auth0.com)
	// CAPTCHA_REDIRECT: the URL for the webtask that will show and process CAPTCHA

	// Put a specific client ID if you dont want CAPTCHA for every client
	// if (context.clientID !== '[your client id]')
	<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
	<HTML>
	<HEAD>
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css" integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous">
	<TITLE>
	Hello World
	</TITLE>
	<style>
	function (user, context, callback) {

	// only apply changes for the WS-Fed application
	if (context.clientName !== 'Your ws-fed application name') {
	return callback(null, user, context);
	}

	// exclude the upn claim creation (defaults to true)
	context.samlConfiguration.createUpnClaim = false;