FWLSE4007E: Received bad token from client IBM worklight 7.0 and 401 unauthorized on IBM IHS server
I have build hybrid app and deployed it on IBM mobilefirst server 7.0. App contains android service which used to send data to backend server. After updating the android application on production I am getting
com.worklight.core.auth.ext.DeviceAuthenticator E FWLSE4007E: Received bad token from client. Server token:'ap6oohvlpd3ak1dmfivsqafebp', client token:'9u7ta9r1592qmvphssfclqn2h0'.
and also if I check ihs server then on IHS server I am getting 401 unauthorized. I guess it is because of token which WAS is send to client but in these case token is never going back to client,I think that is the reason I am getting 401 every time and my data not going to back end.
Please help me out to solve my problem..Thanks in advanced.
ibm-mobilefirst websphere-liberty worklight-server ibmhttpserver
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
|
show 1 more comment
I have build hybrid app and deployed it on IBM mobilefirst server 7.0. App contains android service which used to send data to backend server. After updating the android application on production I am getting
com.worklight.core.auth.ext.DeviceAuthenticator E FWLSE4007E: Received bad token from client. Server token:'ap6oohvlpd3ak1dmfivsqafebp', client token:'9u7ta9r1592qmvphssfclqn2h0'.
and also if I check ihs server then on IHS server I am getting 401 unauthorized. I guess it is because of token which WAS is send to client but in these case token is never going back to client,I think that is the reason I am getting 401 every time and my data not going to back end.
Please help me out to solve my problem..Thanks in advanced.
ibm-mobilefirst websphere-liberty worklight-server ibmhttpserver
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
What exactly did you update in the android application? If you uninstall and reinstall, what is the observation?
– Vivin K
Nov 27 '18 at 8:13
@VivinK Nothing changed in updated android application. If I unistall and reinstall the app.Its working fine no bad token error shown. Do you know why
– Nitish Patel
Nov 27 '18 at 8:50
Appears to be a deviceid change. Did anything else change? Mobile OS /
– Vivin K
Nov 27 '18 at 10:44
@VivinK you mean to say Unique Device Id? given as in link ibm.com/support/knowledgecenter/en/SSHS8R_7.0.0/… is nothing changes like Mobile OS etc. Testing on same devices with same OS version. Android version 5.0 on which problem occurs.
– Nitish Patel
Nov 27 '18 at 10:53
@VivinK is there any way to get unique device id which is used by mobilefirst? do you have any idea when its get generated while building the application?
– Nitish Patel
Nov 28 '18 at 6:36
|
show 1 more comment
I have build hybrid app and deployed it on IBM mobilefirst server 7.0. App contains android service which used to send data to backend server. After updating the android application on production I am getting
com.worklight.core.auth.ext.DeviceAuthenticator E FWLSE4007E: Received bad token from client. Server token:'ap6oohvlpd3ak1dmfivsqafebp', client token:'9u7ta9r1592qmvphssfclqn2h0'.
and also if I check ihs server then on IHS server I am getting 401 unauthorized. I guess it is because of token which WAS is send to client but in these case token is never going back to client,I think that is the reason I am getting 401 every time and my data not going to back end.
Please help me out to solve my problem..Thanks in advanced.
ibm-mobilefirst websphere-liberty worklight-server ibmhttpserver
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
I have build hybrid app and deployed it on IBM mobilefirst server 7.0. App contains android service which used to send data to backend server. After updating the android application on production I am getting
com.worklight.core.auth.ext.DeviceAuthenticator E FWLSE4007E: Received bad token from client. Server token:'ap6oohvlpd3ak1dmfivsqafebp', client token:'9u7ta9r1592qmvphssfclqn2h0'.
and also if I check ihs server then on IHS server I am getting 401 unauthorized. I guess it is because of token which WAS is send to client but in these case token is never going back to client,I think that is the reason I am getting 401 every time and my data not going to back end.
Please help me out to solve my problem..Thanks in advanced.
ibm-mobilefirst websphere-liberty worklight-server ibmhttpserver
ibm-mobilefirst websphere-liberty worklight-server ibmhttpserver
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
asked Nov 27 '18 at 7:21
Nitish PatelNitish Patel
42311226
42311226
What exactly did you update in the android application? If you uninstall and reinstall, what is the observation?
– Vivin K
Nov 27 '18 at 8:13
@VivinK Nothing changed in updated android application. If I unistall and reinstall the app.Its working fine no bad token error shown. Do you know why
– Nitish Patel
Nov 27 '18 at 8:50
Appears to be a deviceid change. Did anything else change? Mobile OS /
– Vivin K
Nov 27 '18 at 10:44
@VivinK you mean to say Unique Device Id? given as in link ibm.com/support/knowledgecenter/en/SSHS8R_7.0.0/… is nothing changes like Mobile OS etc. Testing on same devices with same OS version. Android version 5.0 on which problem occurs.
– Nitish Patel
Nov 27 '18 at 10:53
@VivinK is there any way to get unique device id which is used by mobilefirst? do you have any idea when its get generated while building the application?
– Nitish Patel
Nov 28 '18 at 6:36
|
show 1 more comment
What exactly did you update in the android application? If you uninstall and reinstall, what is the observation?
– Vivin K
Nov 27 '18 at 8:13
@VivinK Nothing changed in updated android application. If I unistall and reinstall the app.Its working fine no bad token error shown. Do you know why
– Nitish Patel
Nov 27 '18 at 8:50
Appears to be a deviceid change. Did anything else change? Mobile OS /
– Vivin K
Nov 27 '18 at 10:44
@VivinK you mean to say Unique Device Id? given as in link ibm.com/support/knowledgecenter/en/SSHS8R_7.0.0/… is nothing changes like Mobile OS etc. Testing on same devices with same OS version. Android version 5.0 on which problem occurs.
– Nitish Patel
Nov 27 '18 at 10:53
@VivinK is there any way to get unique device id which is used by mobilefirst? do you have any idea when its get generated while building the application?
– Nitish Patel
Nov 28 '18 at 6:36
What exactly did you update in the android application? If you uninstall and reinstall, what is the observation?
– Vivin K
Nov 27 '18 at 8:13
What exactly did you update in the android application? If you uninstall and reinstall, what is the observation?
– Vivin K
Nov 27 '18 at 8:13
@VivinK Nothing changed in updated android application. If I unistall and reinstall the app.Its working fine no bad token error shown. Do you know why
– Nitish Patel
Nov 27 '18 at 8:50
@VivinK Nothing changed in updated android application. If I unistall and reinstall the app.Its working fine no bad token error shown. Do you know why
– Nitish Patel
Nov 27 '18 at 8:50
Appears to be a deviceid change. Did anything else change? Mobile OS /
– Vivin K
Nov 27 '18 at 10:44
Appears to be a deviceid change. Did anything else change? Mobile OS /
– Vivin K
Nov 27 '18 at 10:44
@VivinK you mean to say Unique Device Id? given as in link ibm.com/support/knowledgecenter/en/SSHS8R_7.0.0/… is nothing changes like Mobile OS etc. Testing on same devices with same OS version. Android version 5.0 on which problem occurs.
– Nitish Patel
Nov 27 '18 at 10:53
@VivinK you mean to say Unique Device Id? given as in link ibm.com/support/knowledgecenter/en/SSHS8R_7.0.0/… is nothing changes like Mobile OS etc. Testing on same devices with same OS version. Android version 5.0 on which problem occurs.
– Nitish Patel
Nov 27 '18 at 10:53
@VivinK is there any way to get unique device id which is used by mobilefirst? do you have any idea when its get generated while building the application?
– Nitish Patel
Nov 28 '18 at 6:36
@VivinK is there any way to get unique device id which is used by mobilefirst? do you have any idea when its get generated while building the application?
– Nitish Patel
Nov 28 '18 at 6:36
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53494586%2ffwlse4007e-received-bad-token-from-client-ibm-worklight-7-0-and-401-unauthorize%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53494586%2ffwlse4007e-received-bad-token-from-client-ibm-worklight-7-0-and-401-unauthorize%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What exactly did you update in the android application? If you uninstall and reinstall, what is the observation?
– Vivin K
Nov 27 '18 at 8:13
@VivinK Nothing changed in updated android application. If I unistall and reinstall the app.Its working fine no bad token error shown. Do you know why
– Nitish Patel
Nov 27 '18 at 8:50
Appears to be a deviceid change. Did anything else change? Mobile OS /
– Vivin K
Nov 27 '18 at 10:44
@VivinK you mean to say Unique Device Id? given as in link ibm.com/support/knowledgecenter/en/SSHS8R_7.0.0/… is nothing changes like Mobile OS etc. Testing on same devices with same OS version. Android version 5.0 on which problem occurs.
– Nitish Patel
Nov 27 '18 at 10:53
@VivinK is there any way to get unique device id which is used by mobilefirst? do you have any idea when its get generated while building the application?
– Nitish Patel
Nov 28 '18 at 6:36