User story #10101: Rudder server remote run api should bypass ssl verification - Rudder - Issue Tracker

Actions

Copy link

User story #10101

closed

User story #9714: Remote run API should use relay API

Rudder server remote run api should bypass ssl verification

Added by Vincent MEMBRÉ almost 8 years ago. Updated almost 8 years ago.

Status:

Released

Priority:

1 (highest)

Assignee:

François ARMAND

Category:

API

Target version:

4.1.0~beta2

Pull Request:

https://github.com/Normation/rudder/p...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

Since there is no way to provide a valid (not self signed) certificate to use in request ssl verification.

Remote run api now use relay api and they do not work now because of ssl validation.

we should bypass for now this validation until we have a way to provide a certificate

Actions

Copy link

Updated by Vincent MEMBRÉ almost 8 years ago

Status changed from New to In progress

Actions

Copy link

Updated by Vincent MEMBRÉ almost 8 years ago

Status changed from In progress to Pending technical review
Assignee changed from Vincent MEMBRÉ to François ARMAND
Pull Request set to https://github.com/Normation/rudder/pull/1469

PR https://github.com/Normation/rudder/pull/1469

Actions

Copy link

Updated by François ARMAND almost 8 years ago

More context: we want to be able to use Rudder out of the box. Today, several Rudder internal tools usages (curl) already don't check certificate chain. And for now, we don't support rudder web application in a different server than the relay-api (i.e: it may works, but it is not yet officially supported).

When we will want to do the check, we will need to add a configuration option somewhere (configuration file, most likely).

Actions

Copy link