-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
401 authentication-error! But not with curl #107
Comments
I just experienced that using the non-Preemptive works for me, but unfortunately this is not supported in this version.
|
The JIRA API has changed, so this should work in the next release |
thanks for the quick reply. Any information on when this is going to happen? Or is there any version I can already work with? |
Not at this stage |
Do you have a reference to a PR/commit? Then i can cherry-pick and work with a customized version until you released it. |
I’d be happy to have your collaboration - I’ll ping you when something is
available
On Thu, 14 May 2020 at 08:48, Thomas H. ***@***.***> wrote:
Do you have a reference to a PR/commit? Then i can cherry-pick and work
with a customized version until you released it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#107 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAANVMV4C6XKB4JOKRDBYSTRROO3XANCNFSM4M74NGHA>
.
--
…___________________________________________________
John Smart | Wakaleo Consulting | +44 7398 832273
Making smart teams collaborate better
http://johnfergusonsmart.com | [email protected]
___________________________________________________
We love breaking down silos and helping smart teams collaborate better! Ask
about our tailored on-site workshops
<https://johnfergusonsmart.com/training/> in Agile Product Planning
<http://johnfergusonsmart.com/programs-courses/next-generation-agile-delivery-product-planning/>,
BDD Requirements Discovery
<http://johnfergusonsmart.com/programs-courses/mastering-agile-requirements-behaviour-driven-development/>,
BDD, TDD and Clean Coding
<http://johnfergusonsmart.com/programs-courses/bdd-tdd-clean-coding/>,
and Advanced
BDD Test Automation
<http://johnfergusonsmart.com/programs-courses/advanced-bdd-test-automation/>
.
Need some help with Serenity BDD? Check out our Serenity BDD training and
support packages here <https://johnfergusonsmart.com/serenity-bdd/>.
___________________________________________________
|
alright! Thank you! I`m ready to assist anytime. |
Has this been addressed already? |
Hi @wakaleo , is this issued addressed already? because I'm getting 401 authentication error. |
No, the module needs to be updated/rewritten to work with the new JIRA APIs. |
Thanks @wakaleo for your quick response. |
It depends on what you want to do with JIRA. |
I am using serenity-bdd so once my script pass then I want to update my test case automatically. I've done all the steps as mentioned here https://serenity-bdd.github.io/theserenitybook/latest/jira.html. my test case is pass but I'm getting below error. |
You can (a) wait until the plugin is updated, (b) update the plugin yourself, or (c) write your own integration code in an @after hook method. |
Thanks @wakaleo . I will try this. |
This might not be an issue, but more a problem to me - but I couldn't find anything better to post it.
I just integrated the latest version of the
serenity-jira-plugin
into my project:`
ext {
serenityCoreVersion = '2.2.2'
serenityCucumberVersion = '2.2.2'
}
dependencies {
implementation 'org.jetbrains.kotlin:kotlin-stdlib-jdk8'
testImplementation "net.serenity-bdd:serenity-core:${serenityCoreVersion}"
testImplementation("net.serenity-bdd:serenity-cucumber5:${serenityCucumberVersion}") {
exclude group: 'io.cucumber', module: 'cucumber-java'
}
testImplementation "io.cucumber:cucumber-java8:5.6.0"
testImplementation "net.serenity-bdd:serenity-rest-assured:${serenityCucumberVersion}"
testImplementation "net.serenity-bdd:serenity-jira-plugin:1.12.0"
testImplementation "net.serenity-bdd:serenity-jira-requirements-provider:1.12.0"
`
My serenity.properties have been configured as follows:
jira.url = https://my-company.atlassian.net jira.project = BC jira.username = [email protected] jira.password = myS3cr3tApiToken
Unfortunately I receive a 401:
Authentication error (401) for user [email protected]
If I run the same with curl, everything works fine:
curl --user [email protected]:myS3cr3tApiToken https://my-company.atlassian.net/rest/api/latest/search
What can be the cause for that?
I work with Kotlin and therefor used the cucumber-java8, but as I'm on the jersey-level I cannot image that this conflicts in a way. Updating to latest jersey client 2.30.1 also didn`t solve it.
Any help would be appreciated
The text was updated successfully, but these errors were encountered: