How to use openconnect with username and password at a line in terminal?

up vote
0
down vote

favorite

I use openconnect in Ubuntu 16.04 terminally, when I want to enable it, I need to enter three phases that contain the:

"yes/no"

"username"

"password"

How can I bypass these phases by using openconnect at a line (e.g. using openconnect options)?

Is there any options for that such as following?

sudo openconnect <server-name> --user=<'username'> --pass=<'password'>

I used openconnect --help and found a way for username, but for password and ssl verification have problem yet.

edited Jul 20 at 8:44

asked Jun 2 at 19:43

Benyamin Jafari

17012

add a commentÂ |Â

up vote
0
down vote

favorite

I use openconnect in Ubuntu 16.04 terminally, when I want to enable it, I need to enter three phases that contain the:

"yes/no"

"username"

"password"

How can I bypass these phases by using openconnect at a line (e.g. using openconnect options)?

Is there any options for that such as following?

sudo openconnect <server-name> --user=<'username'> --pass=<'password'>

I used openconnect --help and found a way for username, but for password and ssl verification have problem yet.

edited Jul 20 at 8:44

asked Jun 2 at 19:43

Benyamin Jafari

17012

add a commentÂ |Â

up vote
0
down vote

favorite

I use openconnect in Ubuntu 16.04 terminally, when I want to enable it, I need to enter three phases that contain the:

"yes/no"

"username"

"password"

How can I bypass these phases by using openconnect at a line (e.g. using openconnect options)?

Is there any options for that such as following?

sudo openconnect <server-name> --user=<'username'> --pass=<'password'>

I used openconnect --help and found a way for username, but for password and ssl verification have problem yet.

edited Jul 20 at 8:44

asked Jun 2 at 19:43

Benyamin Jafari

17012

I use openconnect in Ubuntu 16.04 terminally, when I want to enable it, I need to enter three phases that contain the:

"yes/no"

"username"

"password"

How can I bypass these phases by using openconnect at a line (e.g. using openconnect options)?

Is there any options for that such as following?

sudo openconnect <server-name> --user=<'username'> --pass=<'password'>

I used openconnect --help and found a way for username, but for password and ssl verification have problem yet.

edited Jul 20 at 8:44

asked Jun 2 at 19:43

Benyamin Jafari

17012

edited Jul 20 at 8:44

asked Jun 2 at 19:43

Benyamin Jafari

17012

asked Jun 2 at 19:43

Benyamin Jafari

17012

asked Jun 2 at 19:43

Benyamin Jafari

17012

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
1
down vote

accepted

If you type man openconnect in a terminal you will get a manual page describing usage.

Relevant sections:

-u,--user=NAME

Set login username to NAME

--passwd-on-stdin

Read password from standard input

Additionally, you may need to disable certificate warnings:

--no-cert-check

Do not require server SSL certificate to be valid. Checks will still happen and failures will cause a warning message, but the connection will continue anyway. You should not need to use this option - if your servers have SSL certificates which are not signed by a trusted Certificate Authority, you can still add them (or your private CA) to a local file and use that file with the --cafile option.

Or you could add the certificate to a file.

All this can be combined:

echo "password" | sudo openconnect server --user=username --passwd-on-stdin --no-cert-check

edited Jun 2 at 20:59

Benyamin Jafari

17012

answered Jun 2 at 20:39

vidarlo

6,98042139

Thanks, it works, but needed the sudo.
â€“Â Benyamin Jafari
Jun 2 at 20:55

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
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: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');

var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);

;
$window.on('scroll', onScroll);

);

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1043024%2fhow-to-use-openconnect-with-username-and-password-at-a-line-in-terminal%23new-answer', 'question_page');

);

Post as a guest

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
1
down vote

accepted

If you type man openconnect in a terminal you will get a manual page describing usage.

Relevant sections:

-u,--user=NAME

Set login username to NAME

--passwd-on-stdin

Read password from standard input

Additionally, you may need to disable certificate warnings:

--no-cert-check

Do not require server SSL certificate to be valid. Checks will still happen and failures will cause a warning message, but the connection will continue anyway. You should not need to use this option - if your servers have SSL certificates which are not signed by a trusted Certificate Authority, you can still add them (or your private CA) to a local file and use that file with the --cafile option.

Or you could add the certificate to a file.

All this can be combined:

echo "password" | sudo openconnect server --user=username --passwd-on-stdin --no-cert-check

edited Jun 2 at 20:59

Benyamin Jafari

17012

answered Jun 2 at 20:39

vidarlo

6,98042139

Thanks, it works, but needed the sudo.
â€“Â Benyamin Jafari
Jun 2 at 20:55

add a commentÂ |Â

up vote
1
down vote

accepted

If you type man openconnect in a terminal you will get a manual page describing usage.

Relevant sections:

-u,--user=NAME

Set login username to NAME

--passwd-on-stdin

Read password from standard input

Additionally, you may need to disable certificate warnings:

--no-cert-check

Do not require server SSL certificate to be valid. Checks will still happen and failures will cause a warning message, but the connection will continue anyway. You should not need to use this option - if your servers have SSL certificates which are not signed by a trusted Certificate Authority, you can still add them (or your private CA) to a local file and use that file with the --cafile option.

Or you could add the certificate to a file.

All this can be combined:

echo "password" | sudo openconnect server --user=username --passwd-on-stdin --no-cert-check

edited Jun 2 at 20:59

Benyamin Jafari

17012

answered Jun 2 at 20:39

vidarlo

6,98042139

Thanks, it works, but needed the sudo.
â€“Â Benyamin Jafari
Jun 2 at 20:55

add a commentÂ |Â

up vote
1
down vote

accepted

If you type man openconnect in a terminal you will get a manual page describing usage.

Relevant sections:

-u,--user=NAME

Set login username to NAME

--passwd-on-stdin

Read password from standard input

Additionally, you may need to disable certificate warnings:

--no-cert-check

Do not require server SSL certificate to be valid. Checks will still happen and failures will cause a warning message, but the connection will continue anyway. You should not need to use this option - if your servers have SSL certificates which are not signed by a trusted Certificate Authority, you can still add them (or your private CA) to a local file and use that file with the --cafile option.

Or you could add the certificate to a file.

All this can be combined:

echo "password" | sudo openconnect server --user=username --passwd-on-stdin --no-cert-check

edited Jun 2 at 20:59

Benyamin Jafari

17012

answered Jun 2 at 20:39

vidarlo

6,98042139

If you type man openconnect in a terminal you will get a manual page describing usage.

Relevant sections:

-u,--user=NAME

Set login username to NAME

--passwd-on-stdin

Read password from standard input

Additionally, you may need to disable certificate warnings:

--no-cert-check

Do not require server SSL certificate to be valid. Checks will still happen and failures will cause a warning message, but the connection will continue anyway. You should not need to use this option - if your servers have SSL certificates which are not signed by a trusted Certificate Authority, you can still add them (or your private CA) to a local file and use that file with the --cafile option.

Or you could add the certificate to a file.

All this can be combined:

echo "password" | sudo openconnect server --user=username --passwd-on-stdin --no-cert-check

edited Jun 2 at 20:59

Benyamin Jafari

17012

answered Jun 2 at 20:39

vidarlo

6,98042139

edited Jun 2 at 20:59

Benyamin Jafari

17012

edited Jun 2 at 20:59

Benyamin Jafari

17012

edited Jun 2 at 20:59

Benyamin Jafari

17012

answered Jun 2 at 20:39

vidarlo

6,98042139

answered Jun 2 at 20:39

vidarlo

6,98042139

answered Jun 2 at 20:39

vidarlo

6,98042139

Thanks, it works, but needed the sudo.
â€“Â Benyamin Jafari
Jun 2 at 20:55

add a commentÂ |Â

Thanks, it works, but needed the sudo.
â€“Â Benyamin Jafari
Jun 2 at 20:55

Thanks, it works, but needed the sudo.
â€“Â Benyamin Jafari
Jun 2 at 20:55

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Sign up or log in

Post as a guest

Name

Sign up or log in

Name

搜尋此網誌

Gfilui