Skip to content

Instantly share code, notes, and snippets.

##################### ElasticSearch Configuration Example #####################
# This file contains an overview of various configuration settings,
# targeted at operations staff. Application developers should
# consult the guide at <http://elasticsearch.org/guide>.
#
# The installation procedure is covered at
# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
#
# ElasticSearch comes with reasonable defaults for most settings,
#!/bin/bash
#install sublime
which subl > /dev/null 2>&1
if [ $? -ne 0 ]; then
echo 'Installing sublime 3'
add-apt-repository ppa:webupd8team/sublime-text-3
apt-get update
apt-get install -y sublime-text-installer
fi
#!/bin/sh
#
# chkconfig: 2345 55 25
# Description: Nginx init.d script, put in /etc/init.d, chmod +x /etc/init.d/nginx
# For Debian, run: update-rc.d -f nginx defaults
# For CentOS, run: chkconfig --add nginx
#
### BEGIN INIT INFO
# Provides: nginx
# Required-Start: $all
KeycloakKEYCLOAK-405
Feature that doesn't allow old password to be reused
https://issues.jboss.org/browse/KEYCLOAK-405
Issues with proposed implementation: I had almost finished with this but it looked too cumbersome to me.
If the policy is set with value of N = 3.
* For each password reset, fetch all credentials and iterate for credential type "PASSWORD".
* Compare new credential's value with the passowrd of most recently set PASSWORD type credential (There will be only one such credential).
Aim: Configurable policy to Restrict user from using N old passwords again.
https://issues.jboss.org/browse/KEYCLOAK-405
The proposed implementation via "createdDate" : I had almost finished doing this but then it din't look good to me.
Each time a user logins, we are required to
* Fetch all user credential entities and iterate to check the Credential type PASSWORD and check if it matches with the new password being set.
* if the policy is set, fetch all credential entities and iterate to check PASSWORD_EXPIRED type.
* Sort the fetched credentials on the basis of date directly via query or via utility (Collections.sort(...) etc.)
protected String self; // link
protected String id;
protected String username;
protected boolean enabled;
protected boolean totp;
protected boolean emailVerified;
protected String firstName;
protected String lastName;
protected String email;
protected String federationLink;
module.factory('RealmEvents', function($resource) {
return $resource(authUrl + '/admin/realms/:id/events', {
id : '@realm'
});
});
//-------------------------------------------------------------app.js-----------------------------------------------------------
module.filter('unique', function() {
return function(collection, keyname) {
<div class="form-group">
<label class="col-sm-2 control-label"for="username">Username <span class="required" data-ng-show="create">*</span></label>
<div class="col-sm-5">
<!-- Characters >,<,/,\ are forbidden in username -->
<input class="form-control" type="text" id="username" name="username" data-ng-model="user.username" autofocus
required ng-pattern="/^[^\<\>\\\/A-Z]*$/" data-ng-readonly="!create">
</div>
<span tooltip-placement="right" tooltip="Username must be in lowercase and is a case insensitive account identifier. Characters >,<,/,\ are forbidden in username" class="fa fa-info-circle"></span>
</div>
------------------------Updated-----------------------------------------------------
<bouncycastle.crypto.version>1.50</bouncycastle.crypto.version>
<bouncycastle.mail.version>1.46</bouncycastle.mail.version>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15on</artifactId>
<version>${bouncycastle.crypto.version}</version>
</dependency>
<dependency>
"eventListener": {
"sys-logging": {
"protocol": "udp",
"host":"192.162.10.1",
"port":514
}
}
-------------------------------------