# HEA Keychain
[Research Informatics Shared Resource](https://risr.hci.utah.edu), [Huntsman Cancer Institute](https://hci.utah.edu),
Salt Lake City, UT
The HEA server Keychain is a service for managing laboratory and user credentials.
## Version 1.5.0
* Removed integration tests because they are too duplicative of the unit tests.
* Added /credentialsviews endpoint.
* Don't raise boto3 ClientError when trying to delete policies for a role that has already been deleted. There's a good chance the policies are gone too.
## Version 1.4.4
* Bug fix for Managed Credentials not being deleted after expiring.
## Version 1.4.3
* Caching optimizations.
## Version 1.4.2
* Display the role and shares properties again.
## Version 1.4.1
* Use the /credentials endpoint to delete the managed credential not /awscredentials.
## Version 1.4.0
* Fixed issue where credentials were inadvertently deleted.
* Made DELETE call for deleting managed AWS credentials more like other HEA microservices.
## Version 1.3.4
* Changes in naming of menu items for credentials and updated associated icons
* Generated Managed Credential's now outputs the expiration for users to copy to clipboard.
## Version 1.3.3
* Making AWS Credential Username unique per account.
## Version 1.3.2
* Upgrading dependencies to get bug fixes affecting creating and deleting Managed Credentials.
* Increased delay of background task that checks to see if credentials are expired.
## Version 1.3.1
* Introduces Managed Credentials with ability create and specify life span of credential
## Version 1.3.0
* Now all Credentials objects have a role attribute, replacing the old AWSCredentials role_arn attribute.
## Version 1.2.0
* Display type display name in properties card.
## Version 1.1.0
* Pass desktop object permissions back to clients.
* Return type_display_name attribute from GET calls.
## Version 1.0.3
* Improved performance.
## Version 1.0.2
* Added endpoint and links for generating an AWS CLI .aws/credentials file.
## Version 1.0.1
* Improved performance.
## Version 1
Initial release.
## Runtime requirements
* Python 3.10 or 3.11
## Development environment
### Build requirements
* Any development environment is fine.
* On Windows, you also will need:
* Build Tools for Visual Studio 2019, found at https://visualstudio.microsoft.com/downloads/. Select the C++ tools.
* git, found at https://git-scm.com/download/win.
* On Mac, Xcode or the command line developer tools is required, found in the Apple Store app.
* Python 3.10 or 3.11: Download and install Python 3.10 from https://www.python.org, and select the options to install
for all users and add Python to your environment variables. The install for all users option will help keep you from
accidentally installing packages into your Python installation's site-packages directory instead of to your virtualenv
environment, described below.
* Create a virtualenv environment using the `python -m venv <venv_directory>` command, substituting `<venv_directory>`
with the directory name of your virtual environment. Run `source <venv_directory>/bin/activate` (or `<venv_directory>/Scripts/activate` on Windows) to activate the virtual
environment. You will need to activate the virtualenv every time before starting work, or your IDE may be able to do
this for you automatically. **Note that PyCharm will do this for you, but you have to create a new Terminal panel
after you newly configure a project with your virtualenv.**
* From the project's root directory, and using the activated virtualenv, run `pip install wheel` followed by
`pip install -r requirements_dev.txt`. **Do NOT run `python setup.py develop`. It will break your environment.**
### Running tests
Run tests with the `pytest` command from the project root directory. To improve performance, run tests in multiple
processes with `pytest -n auto`.
### Versioning
Use semantic versioning as described in
https://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme. In addition,
while development is underway, the version should be the next version number suffixed by `.dev`.
### Version tags in git
Version tags should follow the format `heaserver-keychains-<version>`, for example, `heaserver-keychains-1.0.0`.
### Uploading to an index server
The following instructions assume separate stable and staging indexes. Numbered releases, including alphas and betas, go
into the stable index. Snapshots of works in progress go into the staging index. Thus, use staging to upload numbered
releases, verify the uploaded packages, and then upload to stable.
From the project's root directory:
1. For numbered releases, remove `.dev` from the version number in setup.py, tag it in git to indicate a release,
and commit to version control. Skip this step for developer snapshot releases.
2. Run `python setup.py clean --all sdist bdist_wheel` to create the artifacts.
3. Run `twine upload -r <repository> dist/<wheel-filename> dist/<tarball-filename>` to upload to the
repository. The repository name has to be defined in a twine configuration file such as `$HOME/.pypirc`.
4. For numbered releases, increment the version number in setup.py, append `.dev` to it, and commit to version
control with a commit message like, "Prepare for next development iteration."
Raw data
{
"_id": null,
"home_page": "https://risr.hci.utah.edu",
"name": "heaserver-keychain",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.10",
"maintainer_email": null,
"keywords": "heaserver-keychain, microservice, healthcare, cancer, research, informatics",
"author": "Research Informatics Shared Resource, Huntsman Cancer Institute, Salt Lake City, UT",
"author_email": "Andrew.Post@hci.utah.edu",
"download_url": "https://files.pythonhosted.org/packages/84/0b/ba4f1bb169beff61fd591231ff0771151ca2c62175095e0f368dc87950cd/heaserver_keychain-1.5.0.tar.gz",
"platform": null,
"description": "# HEA Keychain\r\n[Research Informatics Shared Resource](https://risr.hci.utah.edu), [Huntsman Cancer Institute](https://hci.utah.edu),\r\nSalt Lake City, UT\r\n\r\nThe HEA server Keychain is a service for managing laboratory and user credentials.\r\n\r\n## Version 1.5.0\r\n* Removed integration tests because they are too duplicative of the unit tests.\r\n* Added /credentialsviews endpoint.\r\n* Don't raise boto3 ClientError when trying to delete policies for a role that has already been deleted. There's a good chance the policies are gone too.\r\n\r\n## Version 1.4.4\r\n* Bug fix for Managed Credentials not being deleted after expiring.\r\n\r\n## Version 1.4.3\r\n* Caching optimizations.\r\n\r\n## Version 1.4.2\r\n* Display the role and shares properties again.\r\n\r\n## Version 1.4.1\r\n* Use the /credentials endpoint to delete the managed credential not /awscredentials.\r\n\r\n## Version 1.4.0\r\n* Fixed issue where credentials were inadvertently deleted.\r\n* Made DELETE call for deleting managed AWS credentials more like other HEA microservices.\r\n\r\n## Version 1.3.4\r\n* Changes in naming of menu items for credentials and updated associated icons\r\n* Generated Managed Credential's now outputs the expiration for users to copy to clipboard. \r\n\r\n## Version 1.3.3\r\n* Making AWS Credential Username unique per account.\r\n\r\n## Version 1.3.2\r\n* Upgrading dependencies to get bug fixes affecting creating and deleting Managed Credentials.\r\n* Increased delay of background task that checks to see if credentials are expired.\r\n\r\n## Version 1.3.1\r\n* Introduces Managed Credentials with ability create and specify life span of credential \r\n\r\n## Version 1.3.0\r\n* Now all Credentials objects have a role attribute, replacing the old AWSCredentials role_arn attribute.\r\n\r\n## Version 1.2.0\r\n* Display type display name in properties card.\r\n\r\n## Version 1.1.0\r\n* Pass desktop object permissions back to clients.\r\n* Return type_display_name attribute from GET calls.\r\n\r\n## Version 1.0.3\r\n* Improved performance.\r\n\r\n## Version 1.0.2\r\n* Added endpoint and links for generating an AWS CLI .aws/credentials file.\r\n\r\n## Version 1.0.1\r\n* Improved performance.\r\n\r\n## Version 1\r\nInitial release.\r\n\r\n## Runtime requirements\r\n* Python 3.10 or 3.11\r\n\r\n## Development environment\r\n\r\n### Build requirements\r\n* Any development environment is fine.\r\n* On Windows, you also will need:\r\n * Build Tools for Visual Studio 2019, found at https://visualstudio.microsoft.com/downloads/. Select the C++ tools.\r\n * git, found at https://git-scm.com/download/win.\r\n* On Mac, Xcode or the command line developer tools is required, found in the Apple Store app.\r\n* Python 3.10 or 3.11: Download and install Python 3.10 from https://www.python.org, and select the options to install \r\nfor all users and add Python to your environment variables. The install for all users option will help keep you from \r\naccidentally installing packages into your Python installation's site-packages directory instead of to your virtualenv \r\nenvironment, described below.\r\n* Create a virtualenv environment using the `python -m venv <venv_directory>` command, substituting `<venv_directory>`\r\nwith the directory name of your virtual environment. Run `source <venv_directory>/bin/activate` (or `<venv_directory>/Scripts/activate` on Windows) to activate the virtual\r\nenvironment. You will need to activate the virtualenv every time before starting work, or your IDE may be able to do\r\nthis for you automatically. **Note that PyCharm will do this for you, but you have to create a new Terminal panel\r\nafter you newly configure a project with your virtualenv.**\r\n* From the project's root directory, and using the activated virtualenv, run `pip install wheel` followed by\r\n `pip install -r requirements_dev.txt`. **Do NOT run `python setup.py develop`. It will break your environment.**\r\n\r\n### Running tests\r\nRun tests with the `pytest` command from the project root directory. To improve performance, run tests in multiple\r\nprocesses with `pytest -n auto`.\r\n\r\n### Versioning\r\nUse semantic versioning as described in\r\nhttps://packaging.python.org/guides/distributing-packages-using-setuptools/#choosing-a-versioning-scheme. In addition,\r\nwhile development is underway, the version should be the next version number suffixed by `.dev`.\r\n\r\n### Version tags in git\r\nVersion tags should follow the format `heaserver-keychains-<version>`, for example, `heaserver-keychains-1.0.0`.\r\n\r\n### Uploading to an index server\r\nThe following instructions assume separate stable and staging indexes. Numbered releases, including alphas and betas, go\r\ninto the stable index. Snapshots of works in progress go into the staging index. Thus, use staging to upload numbered\r\nreleases, verify the uploaded packages, and then upload to stable.\r\n\r\nFrom the project's root directory:\r\n1. For numbered releases, remove `.dev` from the version number in setup.py, tag it in git to indicate a release,\r\nand commit to version control. Skip this step for developer snapshot releases.\r\n2. Run `python setup.py clean --all sdist bdist_wheel` to create the artifacts.\r\n3. Run `twine upload -r <repository> dist/<wheel-filename> dist/<tarball-filename>` to upload to the\r\n repository. The repository name has to be defined in a twine configuration file such as `$HOME/.pypirc`.\r\n4. For numbered releases, increment the version number in setup.py, append `.dev` to it, and commit to version\r\ncontrol with a commit message like, \"Prepare for next development iteration.\"\r\n",
"bugtrack_url": null,
"license": null,
"summary": "a service for managing laboratory credentials",
"version": "1.5.0",
"project_urls": {
"Homepage": "https://risr.hci.utah.edu"
},
"split_keywords": [
"heaserver-keychain",
" microservice",
" healthcare",
" cancer",
" research",
" informatics"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "e71789a8c3156eedd3c433bc1dbc2c2780e35d703cd59f081753d9eb633760df",
"md5": "a9e74c7398ff9cc6237136eb62d91144",
"sha256": "3375ae615389dbeba59a8ec371725136cc808d1c1529d84a4e20c334901d4d28"
},
"downloads": -1,
"filename": "heaserver_keychain-1.5.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "a9e74c7398ff9cc6237136eb62d91144",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.10",
"size": 18223,
"upload_time": "2024-11-19T23:03:28",
"upload_time_iso_8601": "2024-11-19T23:03:28.356319Z",
"url": "https://files.pythonhosted.org/packages/e7/17/89a8c3156eedd3c433bc1dbc2c2780e35d703cd59f081753d9eb633760df/heaserver_keychain-1.5.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "840bba4f1bb169beff61fd591231ff0771151ca2c62175095e0f368dc87950cd",
"md5": "2b27938d9b142e606d664d056def6aaf",
"sha256": "746a812dbaf91c7a57210966fac46543ca29bff9d40070a5ece3e0c6e025be54"
},
"downloads": -1,
"filename": "heaserver_keychain-1.5.0.tar.gz",
"has_sig": false,
"md5_digest": "2b27938d9b142e606d664d056def6aaf",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.10",
"size": 27675,
"upload_time": "2024-11-19T23:03:30",
"upload_time_iso_8601": "2024-11-19T23:03:30.261853Z",
"url": "https://files.pythonhosted.org/packages/84/0b/ba4f1bb169beff61fd591231ff0771151ca2c62175095e0f368dc87950cd/heaserver_keychain-1.5.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-11-19 23:03:30",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "heaserver-keychain"
}
JSON