Page MenuHomePhabricator
Create Task
Maniphest T11856

conduit.getcertificate always return ERR-BAD-TOKEN !
Closed, InvalidPublic
Actions

Description

Hi,

First of all a big salute for this wonderful product...

I m trying to get conduit certificate to integrate with Zulip chat server....

I tried

arc --conduit-uri="http://project.MYDOMAINNAME.in:81" install-certificate --trace

It produces following .arcrc file : (only with token, not with certificate )

{
  "hosts": {
    "http://project.MYDOMAINNAME.in:81/api/": {
      "token": "cli-b6otdvecgtynjlgmli6r44zd7kjf"
    }
  }
}

To obtain certificate, I tried following arc call.

echo '{
  "token": "cli-b6otdvecgtynjlgmli6r44zd7kjf",
  "host": "http://project.MYDOMAINNAME.in:81/"
}' | arc call-conduit --conduit-uri http://project.MYDOMAINNAME.in:81/ --conduit-token cli-b6otdvecgtynjlgmli6r44zd7kjf conduit.getcertificate

Output:

{"error":"ERR-BAD-TOKEN","errorMessage":"ERR-BAD-TOKEN: Token does not exist or has expired.","response":null}

But this conduit.getcetificate call always return ERR-BAD-TOKEN no matter what token I m using .... I verified toekn validity from Settings -> Conduit Tokens ... all are valid only!

Please help me.

Thanks in advance!

Event Timeline

baskar007 created this task.Nov 13 2016, 9:08 AM
epriestley closed this task as Invalid.Nov 13 2016, 1:25 PM
epriestley added a subscriber: epriestley.

Certificates have been deprecated in favor of tokens (they were less flexible, and users frequently found working with them confusing). Everything you describe is working as intended, so this is not a bug in Phabricator. We also don't provide support with third-party code.

If you're using a Zulip binding and its instructions tell you to generate a certificate, they are substantially out of date and won't work for a modern version of Phabricator. If you're using these bindings, they're haven't been updated in more than two years.

You should contact the extension maintainers, not us, for help with their extension or configuration instructions.

mpries added a subscriber: mpries.Nov 14 2016, 11:25 AM

Hi,

Everything you describe is working as intended, so this is not a bug in Phabricator.

For me it looks like conduit.getcertificate is not working as intended, otherwise it would return a certificate. The current API documentation still contains this method (and there is no notice, that this is deprecated or removed):
https://secure.phabricator.com/conduit/query/modern/

Where would I be able to see, that this call is not working anymore?

Thanks!

baskar007 added a comment.Nov 15 2016, 3:59 AM
In T11856#200178, @mpries wrote:

Hi,

Everything you describe is working as intended, so this is not a bug in Phabricator.

For me it looks like conduit.getcertificate is not working as intended, otherwise it would return a certificate. The current API documentation still contains this method (and there is no notice, that this is deprecated or removed):
https://secure.phabricator.com/conduit/query/modern/

Where would I be able to see, that this call is not working anymore?

Thanks!

+1

baskar007 added a comment.Nov 15 2016, 4:02 AM
In T11856#200111, @epriestley wrote:

Certificates have been deprecated in favor of tokens (they were less flexible, and users frequently found working with them confusing). Everything you describe is working as intended, so this is not a bug in Phabricator. We also don't provide support with third-party code.

If you're using a Zulip binding and its instructions tell you to generate a certificate, they are substantially out of date and won't work for a modern version of Phabricator. If you're using these bindings, they're haven't been updated in more than two years.

You should contact the extension maintainers, not us, for help with their extension or configuration instructions.

@epriestley Thanks for the reply. Please remove conduite.getcertificate method from modern API list. (or mark it as a deprecated.)

Phabricator · Built by Phacility