credit: https://christianmoser.me/docker-for-mac-beta-insecure-registry-flag/
pinata get daemon > daemon.json.insecure-registry:<ip/domain:port> or inecure-registries:[<ip/domain:prot>,<ip/domain:prot>]pinata set daemon @daemon.jsonpinata restart make sure the Redis work directory is in a partition own free space larger than memory
to avoid BGSAVE fail with a fork() error even with a lot of availbe memory
http://stackoverflow.com/questions/11752544/redis-bgsave-failed-because-fork-cannot-allocate-memory
echo 1 > /proc/sys/vm/overcommit_memory as temporary solution. vm.overcommit_memory=1 to /etc/sysctl.conf and reboot as a long term solutionkeep writing when BGSAVE error
in /etc/redis.conf, add or modify stop-writes-on-bgsave-error no
disable Transparent Huge Pages(THP)
This will create latency and memory usage issue with redis.
Run the following command, and add it to /etc/rc.local to retain the setting after reboot
sudo echo never > /sys/kernel/mm/transparent_hugepage/enabledenlarge TCP backlog setting
Run the following command, and add it to /etc/rc.local to retain the setting after reboot
sysctl -w net.core.somaxconn=65535By installing the first Redis instance, you can use the configuration as template for your 2nd one.
yum install redis
service redis startThis redis instance listens on localhost:6379 by default.
The default redis instance uses /var/lib/redis as its working directory, dumped memory content is saved under this directory with name dump.rdb if you did not change it manually.
to avoid runtime conflict, we need to create a new working directory
mkdir -p /var/lib/redis2/
chown redis /var/lib/redis2/
chgrp redis /var/lib/redis2/Create a new configuration file by copying /etc/redis.conf
cp /etc/redis.conf /etc/redis2.confEdit following settings to avoid conflicts
logfile "/var/log/redis/redis2.log"
dir "/var/lib/redis2"
pidfile "/var/run/redis/redis2.pid"
port 6380Create service file
cp /usr/lib/systemd/system/redis.service /usr/lib/systemd/system/redis2.serviceModify the settings under Service section
[Service]
ExecStart=/usr/bin/redis-server /etc/redis2.conf --daemonize no
ExecStop=/usr/bin/redis-shutdown redis2set to start with boot
systemctl enable redis2start 2nd redis
service redis2 startlsof -i:6379
lsof -i:6380yum install docker-selinuxDocker 1.9 has fixed this issue
sudo yum update curl -sSL https://get.docker.com/ | sh service docker start chkconfig docker on
dj-sso-server is a Django application that provides Single Sign-on feature for your project.
The dj-sso-server application works as a SSO provider , you can use dj-sso-client (https://github.com/feifangit/dj-sso-client) as the SSO client in other projects need SSO.
Install by command pip install dj-sso-server
The dependent package dj-api-auth (https://github.com/feifangit/dj-api-auth) will be installed automatically.
Based on the dj-api-auth module, we can create an API key with SSO related APIs initially included. All the API communications between dj-sso-server and dj-sso-client are protected by dj-api-auth
The API key will also be bind with a host which is used to limit the origin of SSO requests.
SSO work flow with dj-sso-client
Firstly, dj-sso-client applies a request key via API reqeusttoken/ on dj-sso-server
The request key in dj-sso-server side will be kept in cache for 5 minutes, so the whole SSO login process should be done in 5 minutes.
With the request key, dj-sso-client redirects user to SSO login page on SSO provider, and get auth token if login success. dj-sso-server will
- verify the request origin
- verify request key validity (expired?)
- save user information in cache
dj-sso-client verifies the auth token with dj-sso-server via API authtoken/, and get a SSOUser object.
dj-sso-server delete the request key from cache once the authtoken/ is called.
If there's an already logged-in account on dj-sso-server (say, the project where SSO provider is placed also provides other features, and there's a valid cookies in browser side and valid session on server side), user can select to continue with that logged account.
SSO login through dj-sso-server with not affect the login status on dj-sso-server.
Since request keys are stored in cache waiting for verification or expiration. If you have multiple application process running in your deployment (gunicorn etc.), please use proper cache system that can be shared between processes.
Memcached and Redis are both great for caching, be aware, the Local-memory caching (django.core.cache.backends.locmem.LocMemCache) is a toy for local debugging.
# add auth for a browser-oriented view
url(r'^sso/', include("djssoserver.urls"))
#...
optional, a path to function receives an user object and return a json string.
the default SSO_SERVER_USER_TO_JSON_FUNC function is djssoserver.utility.default_user_to_json
def default_user_to_json(user): return json.dumps(model_to_dict(user, exclude=["password", "user_permissions"]), cls=DjangoJSONEncoder)
In order to discover and manage APIs, after dj-sso-server is added in an accessible urls.py, run command python manage.py reloadentrypoints to collect APIs to database.
You can add styles to your own SSO login page. simply create djsso/ssologin.html under the templates folder. Revamp it by imitating the
original page
dj-sso-client gets a SSOUser object whatever the User model is used in SSO provider project.
See detail in README file of dj-sso-client (https://github.com/feifangit/dj-sso-client)
We have a SSO provider application running on Heroku (https://dj-sso-sample.herokuapp.com/).
Source code: under example folder
To try the demo out, check out the README file of dj-sso-client (https://github.com/feifangit/dj-sso-client)
dj-sso-client is the a Django application works as SSO client side of dj-sso-server (https://github.com/feifangit/dj-sso-server)
pip install dj-sso-client
Modify following settings in settings.py of your project
- AUTHENTICATION_BACKENDS, add djssoclient.authbackend.SSOAuthBackend as the backends
- AUTH_USER_MODEL, set djssoclient.SSOUser as user model
AUTHENTICATION_BACKENDS = ('djssoclient.authbackend.SSOAuthBackend',)
AUTH_USER_MODEL = 'djssoclient.SSOUser'
Add following dj-sso-client settings base on your demand
SSO_API_AUTH_SETTING: set API key, SEC key and remote SSO provider URL. This setting is used by underneath dj-api-auth module to proejct API accessing.
SSO_API_AUTH_SETTING = { "apikey": "f4a05287", "seckey": "6a4eeaea54d54f51af703e79c6096d51", "url": "https://dj-sso-sample.herokuapp.com", }SSO_REMOTE_URL_PREFIX (optional): SSO path in remote SSO provider. default /sso/
SSO_USER_STORAGE``(optional): SSOUser storage solution, there are 2 storage backends in ``dj-sso-client already. default: SSOUserDBStorage
- djssoclient.userstorage.SSOUserDBStorage: store user data in database
- djssoclient.userstorage.SSOUserCacheStorage: store user data in cache. You will get better performance.
SSO_SETTING_CACHE (optional): if you selected SSOUserCacheStorage as your user storage backend, and you have more than one cache in settings.py, you can pick up the cache name here. default: default
The default django.core.cache.backends.locmem.LocMemCache stores data per process. In multi-process production environment (gunicorn on multi-core server), it may cause problem while using SSOUserCacheStorage as your user storage engine.
Please use dedicate cache system (Memcached or Redis) as cache backend to avoid this problem.
SSOUser is the user model to store user data. It can be used as database model class if you selected SSOUserDBStorage to be your user storage engine.
class SSOUser(AbstractBaseUser):
username = models.CharField(unique=True, max_length=50)
extras = models.TextField(default="{}")
...
extra user attributes : attributes not exists in the SSOUser class. (attributes except username, password, last_login etc.)
All extra user attributes can be access by getattr method or . operator. And they are stored in class member extras in JSON format.
We already have a SSO provider (dj-sso-server) application running on Heroku: http://dj-sso-sample.herokuapp.com/ . Run the example application in folder example/ssoclient/ locally.
The API key using in the example application is binding with localhost:8000, so make sure you're accessing local application by localhost:8000 rather than the 127.0.0.1:8000.
fresh login
login with existing logged account
switch account