To set git username and password, use the following commands.

$git config --global user.name "Your Name"
$git config --global user.email "youremail@yourdomain.com"

Issue:

While trying to do a repository initialization, the user will be prompted for a password.

Example console log:

Password for 'https://code.rdkcentral.com': remote: Unauthorized fatal: Authentication failed for 'https://<username>@code.rdkcentral.com/r/manifests/'

Possible reasons and solutions:

• Not having a valid RDK Credential

  • Obtain valid RDK credentials : Users must have a valid RDK Central Credentials. To register use the link below

    • RDK Central Registration Link - https://wiki.rdkcentral.com/signup.action

• User registration without valid company email address

  • Users must belong to a licensed company to be able to clone and checkout the manifest. You must register with valid company email address to gain access to manifest if your company is listed as a licensee. To verify if your company is licensed, please check in the following wiki page -  Licensees. 
• Account is inactive/disabled - 
  • Account may have been deactivated/disabled either due to inactivity (60 days) or password has expired - Accounts can be activated using self service. Login to wiki.rdkcentral.com with the username, you will see a message with a link to activate your account. Click on the link to activate your account. If you are still facing issues with activating your account, please email support@rdkcentral.com. Please update your password after it has been activated.
• Account is active, but still getting the password reset error.
  • Unable to login to code.rdkcentral.com  with username (All LOWERCASE) and password -   If you are getting authentication failure, it is possible that your email address is linked with another username that you have used previously or you have logged in to code.rdkcentral.com with a mixed case username. Either case, you can email to support@rdkcentral.com  to mitigate this issue.
  • Able to login to code.rdkcentral.com with username/password - try and browse this repo -https://code.rdkcentral.com/r/admin/repos/components/generic/mediaframework . If you are not able to browse this repo, you can email to support@rdkcentral.com  to mitigate this issue. if you are able to browse the repo, but unable to clone the it is probably  an environment issue. Check your .netrc file

Update the credentials in $HOME/.netrc file, a sample of the file is given below

.netrc

machine code.rdkcentral.com login <user-name> password <Password>

Issue:

In few incidents, the user may not be having the required permission to download the code although having a valid combination of username/password combination.

Example console log:

Username for 'https://code.rdkcentral.com': rdknewuser

Password for 'https://rdknewuser@code.rdkcentral.com':

fatal: remote error: Service not enabled

fatal: cannot obtain manifest https://code.rdkcentral.com/r/manifests

Possible Solution:

Approach RDK support with the necessary approval to get the requested privilege.

Github no more supports direct password login and allows only Personal Access tokens. To generate a new token,

• Goto https://github.com -> Settings -> Developer Settings -> Personal Access Tokens
• Click on Generate a new token. You should be able to see a access new token on your UI.
• Please copy the new token and add it to ~/.netrc file as given below
• machine github.com login <github-handle> password <new github access token>

Eg: machine github.com login sampleuser password ghp_73ozr1OhWvUI1htuRCVwPyWF4Va1234ABCD

GitHub Workflow Steps:

• Create a Fork by simply clicking on the 'fork' button of the repository page on GitHub.
• Clone your Fork, the clone command creates a local git repository from your remote fork on GitHub.
• git clone https://github.com/USERNAME/REPOSITORY.git
• Modify the Code in your local clone, and commit the changes to your local clone using the git commit command.
• Push your Changes by invoking the git push command, from your workspace, to upload your changes to your remote fork on GitHub.
• Create a Pull Request by clicking the 'pull request' button on the GitHub page of your remote fork.

Possible reasons and solutions:

If you are already using the Personal Access Token and getting a 403, chances are that the token has auto-expired.

You can generate a new token in Github by going to "https://github.com -> Settings -> Developer Settings -> Personal Access Tokens", Clicking on "Generate a new token" and then replacing your old token inside the ~/.netrc file with the newly generated one.