May 22 ESI Updates

5.6.0 May 22, 2018

---

Changes

• Update characters_character_killmails_recent to use pagination.
• Update corporations_corporation_killmails_recent to use pagination.

Update BASE_URL

5.5.0 May 3, 2018

---

Changes

• Update BASE_URL to new host of 'https://esi.evetech.net'

April 26/27 Changes

5.4.0 April 28, 2018

---

Additions

• alliances_alliance_contacts_labels
• corporations_corporation_contacts_labels

Changes

• characters_character_wallet_journal (v3 -> v4)
• corporations_corporation_wallets_division_journal (v2 -> v3)

Removals

• characters_character_chat_channels

April 6 ESI Changes

5.3.0 April 12, 2018

---

Additions

• universe_asteroid_belts_asteroid_belt
• Added error message when a character is not authed or is misspelled
• Added usage tip to readme for using functions with multiple characters

Changes

• system_id added to markets_region_orders
• asteroid_belts added to planets object in response from universe_systems_system

Fix endpoints.gs syntax error

5.2.1 April 6, 2018

---

Bug Fixes

• Fix endpoints.gs syntax error

April 3 ESI Changes

5.2.0 April 5, 2018

---

Changes

• REMOVAL GET /legacy/corporations/{corporation_id}/assets/ (v1)
• PROMOTION GET /latest/corporations/{corporation_id}/assets/ (v3)
• PROMOTION GET /latest/characters/{character_id}/notifications/ (v2)
• PROMOTION GET /latest/corporations/{corporation_id}/blueprints/ (v2)
• PROMOTION GET /latest/corporations/{corporation_id}/containers/logs/ (v2)

Bump character/corporation orders endpoints to v2

5.1.0 March 10, 2018

---

Changes

• Bump characters_character_orders to v2.
• Bump corporation_corporation_orders to v2.
• Make it more clear to NOT include the curly braces in your callback url in the dev app

Fix the checkUpdates function

5.0.1 March 7, 2018

---

Bug Fixes

• Renames the app_version constant to fix the checkUpdates function. Thanks @ccp-zoetrope

Auth data storage refactor

5.0.0 March 6, 2018

This major version release focuses on refactoring where SSO auth data (char name/id, corp/alliance id, refresh_token) are stored as well as some QoL improvements for people using the script for corp management.

---

Previously I was relying upon documentProperties service of Google scripts. However, #21 as well as messages from others brought to my attention that it for one reason or another it loses the data every so often. This

This new method creates a new sheet Auth Data within your spreadsheet to store the data, much like a database, one row per character. This allows users to easily export that data and copy paste it back in if something breaks. Or if you want to remove auth of a particular character, just delete their row. This change makes GESI much more reliable and easier to maintain for corp directors and CEOs (or people with a lot of characters).

Changelog & Notes

Breaking Changes

• Reauth of all characters will be required.

Security

By default the Auth Data sheet is hidden and protected so that it is only unhideable/viewable by the sheet owner. i.e. only the sheet owner can see the refresh tokens of people auth'd on that spreadsheet. If you wish to give other people access you will have to manually add them using (Data -> protected sheets and ranges -> show all -> Auth Data -> change permissions and change Only Me to Custom). However auth data can still be retrieved by anyone with edit access by writing a custom function to iterate over the Auth Data sheet and log data.

From my testing, only people with edit access can auth. In terms of corp management, this either means giving each member edit access, have them auth, then revoke edit access to view only or none at all, or only use the sheet for CEO/Director level usage.

If you require absolute security I would suggest the following (i didn't test this so any issues message me):

1. Setup two spreadsheets with GESI. One for CEOs/Directors/Leadership members and another for general members using same client id and secret for each.
2. Replace the authCallback function in the general membership spreadsheet with:

function authCallback(request) {
    return HtmlService.createHtmlOutput('Your refresh token is:  ' + getAccessToken_(request.parameter.code)['refresh_token']);
}

3. Direct corp members to the general membership sheet and have them auth.
4. Have them copy the refresh_token string from the success message and give it to one of their directors/CEO to manually create a row in the leadership/CEO/Director spreadsheet.

This way general members only ever get to see their own refresh_token and the master spreadsheet can be kept secure with only Leadership/CEO/Directors having edit access.

Other

• There is now a function to check for updates, an explanation of each type of update is in the Readme.
• I also added a Troubleshooting section to the readme for common issues i come across and will update as needed.

As usual any issues/etc feel free to get in touch.

Smoke

Return all pages when fetching all pages

4.1.2

Fix #19 again