How to eliminate tracing (prevent Ocp-Apim-Trace) when the call includes a subscription key?
This is a follow up to the following question:
How to prevent Ocp-Apim-Trace: true and ocp-apim-trace-location in production?
My API consumers must have a subscription key to be able to use my API.
However, I do not want them to see the detail traces provided in ocp-apim-trace-location. The detail trace provides them visibility to my internal service URLs and details that can be a potential security risk.
How to eliminate tracing (prevent Ocp-Apim-Trace) when the call includes a subscription key?
azure-api-management
add a comment |
This is a follow up to the following question:
How to prevent Ocp-Apim-Trace: true and ocp-apim-trace-location in production?
My API consumers must have a subscription key to be able to use my API.
However, I do not want them to see the detail traces provided in ocp-apim-trace-location. The detail trace provides them visibility to my internal service URLs and details that can be a potential security risk.
How to eliminate tracing (prevent Ocp-Apim-Trace) when the call includes a subscription key?
azure-api-management
add a comment |
This is a follow up to the following question:
How to prevent Ocp-Apim-Trace: true and ocp-apim-trace-location in production?
My API consumers must have a subscription key to be able to use my API.
However, I do not want them to see the detail traces provided in ocp-apim-trace-location. The detail trace provides them visibility to my internal service URLs and details that can be a potential security risk.
How to eliminate tracing (prevent Ocp-Apim-Trace) when the call includes a subscription key?
azure-api-management
This is a follow up to the following question:
How to prevent Ocp-Apim-Trace: true and ocp-apim-trace-location in production?
My API consumers must have a subscription key to be able to use my API.
However, I do not want them to see the detail traces provided in ocp-apim-trace-location. The detail trace provides them visibility to my internal service URLs and details that can be a potential security risk.
How to eliminate tracing (prevent Ocp-Apim-Trace) when the call includes a subscription key?
azure-api-management
azure-api-management
asked Nov 14 '18 at 19:42
Allan Xu
1,74711837
1,74711837
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is no way to disable tracing funtionality, not sending this header will disable tracing collection for one request only. But do know, that only admin users are capable of collecting traces, if this header is supplied along with subscription key that does not belong to admin account (or no subscription key at all) no traces will be collected. The idea here is that traces may expose information service owner may not be willing to share with developers.
Actually, you could design APIs belong to an open product to be callable anonymously.
Create a new product and uncheck
Require subscription
in its settings. Any API added to such product will be callable without a key anonymously.
So that you could let your consumer anoymously call your API without subscription key and then eliminate tracing.
For more details, you could refer to this article.
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
add a comment |
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%2f53307674%2fhow-to-eliminate-tracing-prevent-ocp-apim-trace-when-the-call-includes-a-subsc%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no way to disable tracing funtionality, not sending this header will disable tracing collection for one request only. But do know, that only admin users are capable of collecting traces, if this header is supplied along with subscription key that does not belong to admin account (or no subscription key at all) no traces will be collected. The idea here is that traces may expose information service owner may not be willing to share with developers.
Actually, you could design APIs belong to an open product to be callable anonymously.
Create a new product and uncheck
Require subscription
in its settings. Any API added to such product will be callable without a key anonymously.
So that you could let your consumer anoymously call your API without subscription key and then eliminate tracing.
For more details, you could refer to this article.
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
add a comment |
There is no way to disable tracing funtionality, not sending this header will disable tracing collection for one request only. But do know, that only admin users are capable of collecting traces, if this header is supplied along with subscription key that does not belong to admin account (or no subscription key at all) no traces will be collected. The idea here is that traces may expose information service owner may not be willing to share with developers.
Actually, you could design APIs belong to an open product to be callable anonymously.
Create a new product and uncheck
Require subscription
in its settings. Any API added to such product will be callable without a key anonymously.
So that you could let your consumer anoymously call your API without subscription key and then eliminate tracing.
For more details, you could refer to this article.
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
add a comment |
There is no way to disable tracing funtionality, not sending this header will disable tracing collection for one request only. But do know, that only admin users are capable of collecting traces, if this header is supplied along with subscription key that does not belong to admin account (or no subscription key at all) no traces will be collected. The idea here is that traces may expose information service owner may not be willing to share with developers.
Actually, you could design APIs belong to an open product to be callable anonymously.
Create a new product and uncheck
Require subscription
in its settings. Any API added to such product will be callable without a key anonymously.
So that you could let your consumer anoymously call your API without subscription key and then eliminate tracing.
For more details, you could refer to this article.
There is no way to disable tracing funtionality, not sending this header will disable tracing collection for one request only. But do know, that only admin users are capable of collecting traces, if this header is supplied along with subscription key that does not belong to admin account (or no subscription key at all) no traces will be collected. The idea here is that traces may expose information service owner may not be willing to share with developers.
Actually, you could design APIs belong to an open product to be callable anonymously.
Create a new product and uncheck
Require subscription
in its settings. Any API added to such product will be callable without a key anonymously.
So that you could let your consumer anoymously call your API without subscription key and then eliminate tracing.
For more details, you could refer to this article.
answered Nov 15 '18 at 2:57
Joey Cai
4,489129
4,489129
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
add a comment |
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Thank you for help. I am an admin in my APIM. Is there any way I can produce a non-admin subscription key, so that I can test the senario you mentioned: if this header is supplied along with subscription key that does not belong to admin account no traces will be collected
– Allan Xu
Nov 15 '18 at 4:49
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
Create a new user, subscribe him to a product, and use his subscription key to make a call. You can do that from Azure portal.
– Vitaliy Kurokhtin
Dec 3 '18 at 18:53
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53307674%2fhow-to-eliminate-tracing-prevent-ocp-apim-trace-when-the-call-includes-a-subsc%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