...
How a Community Connector works
Different steps in the workflow
When different functions are called
When Data Studio shows different user interfaces
Expected user actions at different steps
...
I have managed to create a connector that can invoke an Jira api e.g. https://example.atlassian.net/rest/agile/latest/board/1. The authentication utilised for this purpose is the use of a Key as a Basic token.
When the user starts the connector, they will need to provide a key in this instance. The key needs to be in the format of user_email:token and then base64 encoded.
Currently in the code, i have supplied the base64 key.
The result of this specific query will look something like this:
{
"maxResults": 50,
"startAt": 0,
"total": 1,
"isLast": true,
"values": [
{
"id": 1,
"self": "https://kodevelop.atlassian.net/rest/agile/1.0/board/1",
"name": "GDS board",
"type": "simple",
"location": {
"projectId": 10000,
"displayName": "GDS (GDS)",
"projectName": "GDS",
"projectKey": "GDS",
"projectTypeKey": "software",
"avatarURI": "/secure/projectavatar?size=small&s=small&pid=10000&avatarId=10412",
"name": "GDS (GDS)"
}
}
]
}
Then the response will be parsed and you can pretty much get any data from this and many other apis on the platform.
The next steps are:
Check if there is a function that appscript can support to create a base64 encoded key otherwise will probably have to call an api to do that. I am not sure how secure will that be.
To use oAuth instead of key auth type.