Bug #13825
closed
Remote run does not try to use the system token
Added by Félix DALLIDET about 6 years ago.
Updated almost 5 years ago.
Category:
Server components
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Description
Since 4.3 we should try to use the api token and not the content of ~/.rudder when no token are given in input.
- Target version changed from 4.3.7 to 4.3.8
- Target version changed from 4.3.8 to 4.3.9
- Target version changed from 4.3.9 to 4.3.10
- Target version changed from 4.3.10 to 4.3.11
- Target version changed from 4.3.11 to 4.3.12
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Very Small
- Priority changed from 0 to 57
- Target version changed from 4.3.12 to 4.3.13
- Target version changed from 4.3.13 to 4.3.14
- Priority changed from 57 to 56
- Target version changed from 4.3.14 to 587
- Priority changed from 56 to 55
- Target version changed from 587 to 5.0.13
- Target version changed from 5.0.13 to 5.0.14
- Priority changed from 55 to 53
- Target version changed from 5.0.14 to 5.0.15
- Priority changed from 53 to 52
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Priority changed from 52 to 51
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-agent/pull/265
- Status changed from Pending technical review to Pending release
- Name check changed from To do to Reviewed
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.15 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by