I hereby claim:
- I am abstractj on github.
- I am abstractj (https://keybase.io/abstractj) on keybase.
- I have a public key ASBfGo7shb5SfjU1zcjC4TTW9bKOGbf4zHxRRujNftdcnwo
To claim this, I am signing this object:
{ | |
"openapi": "3.0.3", | |
"info": { | |
"title": "Keycloak Admin REST API", | |
"description": "This is a REST API reference for the Keycloak Admin REST API.", | |
"version": "1.0" | |
}, | |
"tags": [ | |
{ | |
"name": "Attack Detection" |
[root@a0a6ab069db0 /]# rpm -qa | |
crypto-policies-20211116-1.gitae470d6.el8.noarch | |
redhat-release-8.6-0.1.el8.x86_64 | |
filesystem-3.8-6.el8.x86_64 | |
publicsuffix-list-dafsa-20180723-1.el8.noarch | |
pcre2-10.32-2.el8.x86_64 | |
ncurses-libs-6.1-9.20180224.el8.x86_64 | |
glibc-common-2.28-189.1.el8.x86_64 | |
bash-4.4.20-3.el8.x86_64 | |
zlib-1.2.11-18.el8_5.x86_64 |
# is the url for retrieve the openid configuration - normally the <server>/auth/realm/<realm_name> | |
discovery-url: http://localhost:8180/auth/realms/summit | |
# the client id for the 'client' application | |
client-id: go-rest | |
# the interface definition you wish the proxy to listen, all interfaces is specified as ':<port>' | |
listen: 127.0.0.1:4000 | |
# log all incoming requests | |
enable-logging: true | |
# log in json format |
# Start the old vagrant | |
$ vagrant init centos-6.3 | |
$ vagrant up | |
# You should see a message like: | |
# [default] The guest additions on this VM do not match the install version of | |
# VirtualBox! This may cause things such as forwarded ports, shared | |
# folders, and more to not work properly. If any of those things fail on | |
# this machine, please update the guest additions and repackage the | |
# box. |
I hereby claim:
To claim this, I am signing this object:
var crypto = require('crypto'); | |
var cipher = crypto.createCipher( process.argv[2], 'tacos' ); | |
//aes-gcm 256 | |
//key size must be 32 | |
var cipher = crypto.createCipheriv('aes-256-gcm', '3zTvzr3p67VC61jmV54rIYu1545x4TlY', 'X6sIq117H0vR'); | |
var cipher = crypto.createCipher('aes-256-gcm', '3zTvzr3p67VC61jmV54rIYu1545x4TlY'); | |
//aes-gcm 128 |
The goal of this document is to describe how the User Management will be implemented in the Unified Push Server. Currently there is only one user created by default when installing UPS. Having the possibility to create multiple users is a "Must Have" and should be manageable from the Admin Console. Some roles should also be introduced
if (!this.identity.isLoggedIn()) { | |
this.credentials.setUserId(saleAgent.getLoginName()); | |
this.credentials.setPassword(saleAgent.getPassword()); | |
this.identity.login(); | |
} else { | |
throw new RuntimeException("Authentication failed"); | |
} |
console.log('Loading a web page'); | |
var page = require('webpage').create(); | |
var url = 'http://localhost:1947/'; | |
page.viewportSize = { | |
width: 1024, | |
height: 768 | |
}; | |
page.open(url, function (status) { | |
//Page is loaded! | |
var iz, i = 0, queue = {}; |