msaarinen

DOCKER
======

./create_partycrasher_zip.sh

docker build -t partycrasher .

-- docker run gunicorn with local ES
docker run -e ELASTICSEARCH_ALLOW_DELETE_ALL=true -e ELASTICSEARCH_CREATE_INDEXES=true -e ELASTICSEARCH_HOSTS=host.docker.internal -e ELASTICSEARCH_PORT=9200 -e ELASTICSEARCH_REST_HTTP_SCHEME=http -e ELASTICSEARCH_REST_SIGN_REQUESTS_ENABLED=false -e PARTYCRASHER_LOGGER_LEVEL=DEBUG -it --rm  -p 8080:8080 --name partycrasher partycrasher

msaarinen

# vIDM Integration with Action Cards server

ActionCards and HeroCards servers both rely on VMware Identity Manager (vIDM) to authorize
access to their API endpoints.  The ActionCards service has adopted the
[HeroCard authorization flow](https://confluence-euc.eng.vmware.com/display/AP/Hero+Card+vIDM+Authentication+Flow)
to maximize compatibility, such that the same access tokens used to call ActionCards APIs are also
passed through and used to call HeroCards APIs.  Note, however, that this is distinct from user
authentication to third-party connectors, which use their own credentials and authentication flows.

# Remote Application Clients for Development