Skip to content

Commit 0ebaa17

Browse files
committed
(docs) update README to account for discussion post
1 parent c3c4f6b commit 0ebaa17

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -95,8 +95,7 @@ Follow the [installation guide](https://github.com/ankitpokhrel/jira-cli/wiki/In
9595
more [here](https://github.com/ankitpokhrel/jira-cli/discussions/356).
9696
2. Run `jira init`, select installation type as `Cloud`, and provide required details to generate a config file required
9797
for the tool.
98-
3. Run the `jira init`, Select the `Cloud` installation type and then select the `OAuth` authentication type. This will prompt for your Jira App Client ID and Client Secret. You can learn more about how to create a Jira App [here](link-to-a-discussion)
99-
98+
3. Run the `jira init`, Select the `Cloud` installation type and then select the `OAuth` authentication type. This will prompt for your Jira App Client ID and Client Secret. You can learn more about how to create a Jira App [here](https://github.com/ankitpokhrel/jira-cli/discussions/879#discussion-8604411)
10099

101100
#### On-premise installation
102101

@@ -129,7 +128,7 @@ default.
129128
- If you want to use PAT, you need to set `JIRA_AUTH_TYPE` as `bearer`.
130129
- If you want to use `mtls` run `jira init`. Select installation type `Local`, and then select authentication type as `mtls`.
131130
- In case `JIRA_API_TOKEN` variable is set it will be used together with `mtls`.
132-
- If you want to use `oauth` run `jira init`. Select installation type `Cloud`, and then select authentication type as `oauth`.
131+
- If you want to use `oauth` run `jira init`. Select installation type `Cloud`, and then select authentication type as `oauth`.
133132

134133
#### Shell completion
135134

@@ -857,7 +856,7 @@ Sprint 1: 3
857856

858857
- https://jira.atlassian.com/browse/ECO-283
859858
- https://community.developer.atlassian.com/t/oauth-2-0-with-proof-key-for-code-exchange-pkce/80173/3
860-
- The 3LO doesn't support [Proof Key for Code Exchange (PKCE)](https://oauth.net/2/pkce/). Without this support, we would have to share the single distrubuted app's client secret with all the consumers. To avoid the need for globally sharing a client secret, each consumer will need to create a JIRA app to effectively use as a proxy into your Jira cloud instance.
859+
- The 3LO doesn't support [Proof Key for Code Exchange (PKCE)](https://oauth.net/2/pkce/). Without this support, we would have to share the single distrubuted app's client secret with all the consumers. To avoid the need for globally sharing a client secret, each consumer will need to create a JIRA app to effectively use as a proxy into your Jira cloud instance.
861860

862861
## Feature requests
863862

0 commit comments

Comments
 (0)