This GEM prints your API to json in the responses - example below

[kairos0ne]

I've got this gem working with JIRA CLOUD REST API. However I notice that the json response includes the client and all its options including our API key.

Thats a massive security issue for us... I've provided an example of the response that comes back for client.Projects.all. If you are intending to address this we are more than happy to assist in the development changes required to ensure no tokens/passwords are either printed to logs or provided on any responses. Its a real shame because it would be a really nice little Gem otherwise.

{ "client": { "options": { "site": "https://monochrome-development.atlassian.net/", "context_path": "", "rest_base_path": "/rest/api/3", "ssl_verify_mode": 1, "use_ssl": true, "use_client_cert": false, "auth_type": "basic", "http_debug": false, "username": "[email protected]", "password": "REDACTED" }, "request_client": { "options": { "username": "[email protected]", "password": "REDACTED", "site": "https://monochrome-development.atlassian.net/", "context_path": "", "rest_base_path": "/rest/api/3", "ssl_verify_mode": 1, "use_ssl": true, "use_client_cert": false, "auth_type": "basic", "http_debug": false }, "cookies": {}, "authenticated": true }, "http_debug": false, "cache": { "table": {} } }, "attrs": { "expand": "description,lead,issueTypes,url,projectKeys", "self": "https://monochrome-development.atlassian.net/rest/api/3/project/10014", "id": "10014", "key": "CAD", "name": "Cadbury", "avatarUrls": { "48x48": "https://monochrome-development.atlassian.net/secure/projectavatar?avatarId=10324", "24x24": "https://monochrome-development.atlassian.net/secure/projectavatar?size=small&avatarId=10324", "16x16": "https://monochrome-development.atlassian.net/secure/projectavatar?size=xsmall&avatarId=10324", "32x32": "https://monochrome-development.atlassian.net/secure/projectavatar?size=medium&avatarId=10324" }, "projectTypeKey": "software", "simplified": false }, "expanded": false, "deleted": false },

[bobbrodie]

It would definitely be great to obfuscate or remove specific fields on their way back, similar to how Rails can remove specific request params when they're made.

I think we should make it configurable, with specific fields configured by default in the config file.