npgsql connecting to AWS RDS PostgreSQL with SSL
up vote
0
down vote
favorite
npgsql driver supports the following parameter sslrootcert=<<certname>>
? this parameter is not honored in the connection string as there is no effect. I have imported the certificate to the webserver and the updated connection string too.
postgresql amazon-web-services amazon-rds x509certificate npgsql
add a comment |
up vote
0
down vote
favorite
npgsql driver supports the following parameter sslrootcert=<<certname>>
? this parameter is not honored in the connection string as there is no effect. I have imported the certificate to the webserver and the updated connection string too.
postgresql amazon-web-services amazon-rds x509certificate npgsql
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
npgsql driver supports the following parameter sslrootcert=<<certname>>
? this parameter is not honored in the connection string as there is no effect. I have imported the certificate to the webserver and the updated connection string too.
postgresql amazon-web-services amazon-rds x509certificate npgsql
npgsql driver supports the following parameter sslrootcert=<<certname>>
? this parameter is not honored in the connection string as there is no effect. I have imported the certificate to the webserver and the updated connection string too.
postgresql amazon-web-services amazon-rds x509certificate npgsql
postgresql amazon-web-services amazon-rds x509certificate npgsql
edited Nov 19 at 22:29
John Rotenstein
66.4k774118
66.4k774118
asked Nov 19 at 21:14
varun7447
117115
117115
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Npgsql currently doesn't allow specifying a certificate via the connection string, you need to provide the certificate programmatically as described in the docs. An issue already tracks specifying the certificate via the connection string.
BTW, did you see documentation saying you could use sslrootcert=<<certname>>
anywhere with Npgsql?
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameterpsql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Yeah i know they are two different clients but wondering if i just usesslmode
is enough to connect to AWS RDS postgresql using npgsql or if thesslrootcert
is needed for rds
– varun7447
Nov 20 at 20:54
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
|
show 1 more 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',
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%2f53382727%2fnpgsql-connecting-to-aws-rds-postgresql-with-ssl%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
up vote
0
down vote
Npgsql currently doesn't allow specifying a certificate via the connection string, you need to provide the certificate programmatically as described in the docs. An issue already tracks specifying the certificate via the connection string.
BTW, did you see documentation saying you could use sslrootcert=<<certname>>
anywhere with Npgsql?
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameterpsql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Yeah i know they are two different clients but wondering if i just usesslmode
is enough to connect to AWS RDS postgresql using npgsql or if thesslrootcert
is needed for rds
– varun7447
Nov 20 at 20:54
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
|
show 1 more comment
up vote
0
down vote
Npgsql currently doesn't allow specifying a certificate via the connection string, you need to provide the certificate programmatically as described in the docs. An issue already tracks specifying the certificate via the connection string.
BTW, did you see documentation saying you could use sslrootcert=<<certname>>
anywhere with Npgsql?
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameterpsql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Yeah i know they are two different clients but wondering if i just usesslmode
is enough to connect to AWS RDS postgresql using npgsql or if thesslrootcert
is needed for rds
– varun7447
Nov 20 at 20:54
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
|
show 1 more comment
up vote
0
down vote
up vote
0
down vote
Npgsql currently doesn't allow specifying a certificate via the connection string, you need to provide the certificate programmatically as described in the docs. An issue already tracks specifying the certificate via the connection string.
BTW, did you see documentation saying you could use sslrootcert=<<certname>>
anywhere with Npgsql?
Npgsql currently doesn't allow specifying a certificate via the connection string, you need to provide the certificate programmatically as described in the docs. An issue already tracks specifying the certificate via the connection string.
BTW, did you see documentation saying you could use sslrootcert=<<certname>>
anywhere with Npgsql?
answered Nov 20 at 9:52
Shay Rojansky
6,64921743
6,64921743
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameterpsql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Yeah i know they are two different clients but wondering if i just usesslmode
is enough to connect to AWS RDS postgresql using npgsql or if thesslrootcert
is needed for rds
– varun7447
Nov 20 at 20:54
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
|
show 1 more comment
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameterpsql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Yeah i know they are two different clients but wondering if i just usesslmode
is enough to connect to AWS RDS postgresql using npgsql or if thesslrootcert
is needed for rds
– varun7447
Nov 20 at 20:54
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameter
psql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
I don't see any documentation about sslrootcert in any npgsql documentation. I am using npgsql and AWS RDS postgres. One of my requirement is to use SSL and AWS postgres document has sslrootcert as the parameter
psql -h testpg.cdhmuqifdpib.us-east-1.rds.amazonaws.com -p 5432 "dbname=testpg user=testuser sslrootcert=rds-ca-2015-root.pem sslmode=verify-full"
– varun7447
Nov 20 at 19:24
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Options to psql can't be used as-is on Npgsql - they're two different clients. As I wrote above, you can use SSL with Npgsql, but you have to specify the certificate programmatically.
– Shay Rojansky
Nov 20 at 19:45
Yeah i know they are two different clients but wondering if i just use
sslmode
is enough to connect to AWS RDS postgresql using npgsql or if the sslrootcert
is needed for rds– varun7447
Nov 20 at 20:54
Yeah i know they are two different clients but wondering if i just use
sslmode
is enough to connect to AWS RDS postgresql using npgsql or if the sslrootcert
is needed for rds– varun7447
Nov 20 at 20:54
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
RDS is just PostgreSQL, there's nothing special about it really. Apart from that, specifying a root CA certificate is only needed to verify the server's certificate when it is signed by a non-standard CA - usually this isn't required. Clients typically just have to provide their own certificate for authentication at the server. You can read more about all of this in the PostgreSQL docs.
– Shay Rojansky
Nov 20 at 23:02
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
According to AWS document the root certificate is provided by AWS. docs.aws.amazon.com/AmazonRDS/latest/UserGuide/… there is a flag to pass the root certificate. maybe when we import the certificate on to the app server this sslrootcert parameter is not required.
– varun7447
Nov 21 at 0:45
|
show 1 more 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%2f53382727%2fnpgsql-connecting-to-aws-rds-postgresql-with-ssl%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