Why am I obtaining this ERR_CERT_AUTHORITY_INVALID error calling an HTTPS API using a self signed certificate...
I have the following problem trying to call an external REST HTTPS API from an Angular service:
I have this Angular service:
@Injectable()
export class MailDetailProtocolloService {
private protocolloAooApiUrl = 'https://myservercom:443/my_project/api/GetDeparmentsList';
constructor(
private http: HttpClient
)
{
}
/** GET AOO List chiamando un'API esterna */
getAooList(): Observable<Aoo> {
return this.http.get<Aoo>(this.protocolloAooApiUrl)
}
}
The problem is that this API use a self signed certificate and calling it I obtain this error message in the console:
GET https://myservercom:443/my_project/api/GetDeparmentsList net::ERR_CERT_AUTHORITY_INVALID
Why? How can I fix it and call it using this self signed certificate?
angular rxjs angular5 javascript-framework angular-http
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
add a comment |
I have the following problem trying to call an external REST HTTPS API from an Angular service:
I have this Angular service:
@Injectable()
export class MailDetailProtocolloService {
private protocolloAooApiUrl = 'https://myservercom:443/my_project/api/GetDeparmentsList';
constructor(
private http: HttpClient
)
{
}
/** GET AOO List chiamando un'API esterna */
getAooList(): Observable<Aoo> {
return this.http.get<Aoo>(this.protocolloAooApiUrl)
}
}
The problem is that this API use a self signed certificate and calling it I obtain this error message in the console:
GET https://myservercom:443/my_project/api/GetDeparmentsList net::ERR_CERT_AUTHORITY_INVALID
Why? How can I fix it and call it using this self signed certificate?
angular rxjs angular5 javascript-framework angular-http
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
add a comment |
I have the following problem trying to call an external REST HTTPS API from an Angular service:
I have this Angular service:
@Injectable()
export class MailDetailProtocolloService {
private protocolloAooApiUrl = 'https://myservercom:443/my_project/api/GetDeparmentsList';
constructor(
private http: HttpClient
)
{
}
/** GET AOO List chiamando un'API esterna */
getAooList(): Observable<Aoo> {
return this.http.get<Aoo>(this.protocolloAooApiUrl)
}
}
The problem is that this API use a self signed certificate and calling it I obtain this error message in the console:
GET https://myservercom:443/my_project/api/GetDeparmentsList net::ERR_CERT_AUTHORITY_INVALID
Why? How can I fix it and call it using this self signed certificate?
angular rxjs angular5 javascript-framework angular-http
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
I have the following problem trying to call an external REST HTTPS API from an Angular service:
I have this Angular service:
@Injectable()
export class MailDetailProtocolloService {
private protocolloAooApiUrl = 'https://myservercom:443/my_project/api/GetDeparmentsList';
constructor(
private http: HttpClient
)
{
}
/** GET AOO List chiamando un'API esterna */
getAooList(): Observable<Aoo> {
return this.http.get<Aoo>(this.protocolloAooApiUrl)
}
}
The problem is that this API use a self signed certificate and calling it I obtain this error message in the console:
GET https://myservercom:443/my_project/api/GetDeparmentsList net::ERR_CERT_AUTHORITY_INVALID
Why? How can I fix it and call it using this self signed certificate?
angular rxjs angular5 javascript-framework angular-http
angular rxjs angular5 javascript-framework angular-http
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
asked Nov 14 '18 at 15:21
AndreaNobiliAndreaNobili
13.2k57181328
13.2k57181328
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Self-signed certificates aren't accepted by browsers per default. There is a list of trusted certification authorities (short 'CA') installed on your computer that are allowed to issue certificates. In order to have your computer trust your certificate, you have to either add your CA to this trust list manually or install the self-signed certificate directly.
How to do this depends on your operating system and browser.
Here is the tutorial for Windows
Here is the turorial for Mac
Here is the tutorial for Linux
Unlike with "fat clients", there isn't any way to do this automatically with web applications; it's a default security policy for all modern browsers. Imagine a website could send sensitive data in the background to a malicious website.
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
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%2f53303484%2fwhy-am-i-obtaining-this-err-cert-authority-invalid-error-calling-an-https-api-us%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
Self-signed certificates aren't accepted by browsers per default. There is a list of trusted certification authorities (short 'CA') installed on your computer that are allowed to issue certificates. In order to have your computer trust your certificate, you have to either add your CA to this trust list manually or install the self-signed certificate directly.
How to do this depends on your operating system and browser.
Here is the tutorial for Windows
Here is the turorial for Mac
Here is the tutorial for Linux
Unlike with "fat clients", there isn't any way to do this automatically with web applications; it's a default security policy for all modern browsers. Imagine a website could send sensitive data in the background to a malicious website.
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
add a comment |
Self-signed certificates aren't accepted by browsers per default. There is a list of trusted certification authorities (short 'CA') installed on your computer that are allowed to issue certificates. In order to have your computer trust your certificate, you have to either add your CA to this trust list manually or install the self-signed certificate directly.
How to do this depends on your operating system and browser.
Here is the tutorial for Windows
Here is the turorial for Mac
Here is the tutorial for Linux
Unlike with "fat clients", there isn't any way to do this automatically with web applications; it's a default security policy for all modern browsers. Imagine a website could send sensitive data in the background to a malicious website.
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
add a comment |
Self-signed certificates aren't accepted by browsers per default. There is a list of trusted certification authorities (short 'CA') installed on your computer that are allowed to issue certificates. In order to have your computer trust your certificate, you have to either add your CA to this trust list manually or install the self-signed certificate directly.
How to do this depends on your operating system and browser.
Here is the tutorial for Windows
Here is the turorial for Mac
Here is the tutorial for Linux
Unlike with "fat clients", there isn't any way to do this automatically with web applications; it's a default security policy for all modern browsers. Imagine a website could send sensitive data in the background to a malicious website.
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
Self-signed certificates aren't accepted by browsers per default. There is a list of trusted certification authorities (short 'CA') installed on your computer that are allowed to issue certificates. In order to have your computer trust your certificate, you have to either add your CA to this trust list manually or install the self-signed certificate directly.
How to do this depends on your operating system and browser.
Here is the tutorial for Windows
Here is the turorial for Mac
Here is the tutorial for Linux
Unlike with "fat clients", there isn't any way to do this automatically with web applications; it's a default security policy for all modern browsers. Imagine a website could send sensitive data in the background to a malicious website.
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
edited Nov 14 '18 at 16:47
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
answered Nov 14 '18 at 16:07
ggradnigggradnig
3,6431424
3,6431424
add a comment |
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.
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%2f53303484%2fwhy-am-i-obtaining-this-err-cert-authority-invalid-error-calling-an-https-api-us%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
