Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Authorize an Org Using the Web Server Flow
Authorize an Org Using the JWT Bearer Flow
Create a Private Key and Self-Signed Digital Certificate
Create a Connected App for Your Dev Hub Org
Use an Existing Access Token instead of Authorizing
Authorization Information for an Org
Log Out of an Org
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Authorization Information for an Org

You can view information for all orgs that you have authorized and the scratch orgs that you have created.

Use this command to view authentication information about an org.

If you have set a default username, you don’t have to specify the --targetusername parameter. To display the usernames for all the active orgs that you’ve authorized or created, use force:org:list.

If you have set an alias for an org, you can specify it with the --targetusername parameter. This example uses the my-scratch alias.

To get more information, such as the Salesforce DX authentication URL, include the --verbose parameter. However, --verbose displays the Sfdx Auth Url only if you authenticated to the org using auth:web:login and not auth:jwt:grant.

To help prevent security breaches, the force:org:display output doesn’t include the org’s client secret or refresh token. If you need these values, perform an OAuth flow outside of the Salesforce CLI.

Note