Error Updating Machine Specs No Token
Sign in Pricing Blog Support Search GitHub This repository Watch 266 Star 3,550 Fork 964 docker/machine Code Issues 552 Pull requests 22 Projects 0 Wiki Pulse Graphs New issue No way to update Machine parameters (including auth tokens) after create #2206 Open NeilW opened this Issue Nov 6, 2015 · 3 comments Projects None yet Labels kind/enhancement Milestone No milestone Assignees No one assigned 3 participants NeilW commented Nov 6, 2015 The CLI seems to expect credentials stored at create to work forever and doesn't seem to offer a way of updating them other than by manually hacking the JSON file. The Brightbox auth system uses Oauth2 tokens with a single use refresh token to save you storing the passwords in databases. Of course that means when it has been used to retrieve another access token the token needs replacing in the database. Since only the create command does a 'save' this means the token system can't really be used as designed. $ docker-machine ls error getting URL for host example2: Get https://api.gb1.brightbox.com/1.0/servers/srv-ohplp?account_id=acc-tqs4c: oauth2: cannot fetch token: 400 Bad Request Response: {"error":"invalid_grant","error_description":"The provided access grant is invalid, expired, or revoked (e.g. invalid assertion, expired authorization token, bad end-user password credentials, or mismatching authorization code and redirection URI)."} error getting state for host example2: Get https://api.gb1.brightbox.com/1.0/servers/srv-ohplp?account_id=acc-tqs4c: oauth2: cannot fetch token: 400 Bad Request Response: {"error":"invalid_grant","error_description":"The provided access grant is invalid, expired, or revoked (e.g. invalid assertion, expired authorization token, bad end-user password credentials, or mismatching authorization code and redirection URI)."} NAME ACTIVE DRIVER STATE URL SWARM example - brightbox Running tcp://ipv6.srv-rthiy.gb1.brightbox.com:2376 example2 - brightbox Error You have the same issue, obviously, if you revoke the existing credentials or if they simply expire due to lack of use. The workaround at the moment is to avoid storing the token, look for the password in the environment and do a complete re-authentication, but that seems very unsatisfactory. nathanleclaire changed the title from CLI can't seem to handle expired/revoked credentials to No way to update Machine parameters (i
Refunds Application Fees Recipients Country Specs External Accounts Alipay Accounts Bank Accounts Cards Sources Orders Order Items Returns Products SKUs Coupons Discounts Invoices Invoice Items Plans Subscriptions curl Ruby Python PHP Java Node Go Introduction Introduction Topics Authentication Errors Expanding Objects Idempotent Requests Metadata Pagination Request IDs Versioning Core Resources Balance The balance object The balance transaction object Retrieve balance Retrieve a balance transaction List all balance history Charges The charge object Create a charge Retrieve a charge Update https://github.com/docker/machine/issues/2206 a charge Capture a charge List all charges Customers The customer object Create a customer Retrieve a customer Update a customer Delete a customer List all customers Disputes The dispute object The dispute evidence object Retrieve a dispute Update a dispute Close a dispute List all disputes Events The event object Retrieve an https://stripe.com/docs/api event List all events Types of events File Uploads The file upload object Create a file upload Retrieve a file upload List all file uploads Refunds The refund object Create a refund Retrieve a refund Update a refund List all refunds Tokens The token object Create a card token Create a bank account token Create a PII token Retrieve a token Transfers The transfer object Create a transfer Retrieve a transfer Update a transfer List all transfers Types of transfer failures Transfer Reversals The transfer reversal object Create a reversal Retrieve a reversal Update a reversal List all reversals Connect Account The account object Create an account Retrieve account details Update an account Delete an account Reject an account List all connected accounts Application Fee Refunds The application fee refund object Create an application fee refund Retrieve an application fee refund Update an application fee refund List all application fee refunds Application Fees The application fee
Contact Us English Back English 한국어 日本語 Deutsch Italiano Menu Button Search Toggle Submit Search SECURITY PERSPECTIVES https://www.rsa.com/en-us/products-services/identity-access-management/securid/software-tokens PRODUCTS & SERVICES BUSINESS CHALLENGES CUSTOMERS SUPPORT RSA LINK STORE REQUEST A DEMO Company PARTNERS EVENTS Incident Response Contact Us English Privacy | Site Map https://support.laserfiche.com/kb/1013788/list-of-changes-for-quick-fields-10-update-1 Back SECURITY PERSPECTIVES Speaking of Security Blog Industry Perspectives RSA Conference RSA Charge Resource Library Back PRODUCTS & SERVICES Threat Detection and Response Governance, Risk error updating & Compliance Identity and Access Management Fraud Prevention Cybersecurity Framework RSA University RSA Risk and Cybersecurity Practice Back BUSINESS CHALLENGES Third Party Risk IT/Ops Risk Secure Access Identity Lifecycle Cloud Security Network Monitoring Endpoint Monitoring Incident Response Authentication SIEM Back CUSTOMERS Back SUPPORT Back RSA LINK Back STORE Back REQUEST error updating machine A DEMO Back English 한국어 日本語 Deutsch Italiano Identity and Access Management SecurID | RSA Security Token Based Authentication Software Tokens Identity and Access Management SecurID | RSA Security Token Based Authentication Software Tokens RSA SecurID Software Tokens RSA SecurID Software Tokens: Make strong authentication a convenient part of doing business. Deploy RSA software tokens on mobile devices—smartphones, tablets, and PCs— and transform them into intelligent security tokens.
Request a RSA SecurID 90-day/25-user Trial SECURITY SecurID Software Tokens use the same industry-leading time-based algorithm used in RSA SecurID Hardware Tokens. SECURE PROVISIONING Software tokens use a secure provisioning protocol, Cryptographic Token Key Initialization Protocol (CT-KIP), with the option of Quick Response (QR) code provisioning that requires no transmission of confidential token information over the network and can securely bind a token to a device. END-USER CONVENIENCE Software tokens reduce the number of devices users have to manage to