I am going through this apigee tutorial.
When the first time, this script is invoked, it asks for the basic info regrading the user. By mistake, I gave the wrong organisation.
Checking user configuration info ...
Enter the password for user on server
enterprise.apige
e.com.
Password:
Verifying credentials on api.enterprise.apigee.com
...
Organization is invalid!
Please re-run the script
using the right org.
When I re-run the script, it is not asking me for the organisation. How can i set the organisation to the correct name
There is a userconf.sh file in trunk\setup.
Scroll to the top of the file, you will see something like this-
# there are 2 main cases to handle:
# (a) the user's $HOME/.learn-edge.rc file exists,
# in which case we just dot it in; or
# (b) it doesn't exist, in which case we prompt
# for the values and write out to the config file.
Apigee writes all your basic info content in $HOME/.learn-edge.rc. Just modify this-
export org="youraccount-eval"
to the correct value and it will work.
Related
i'm faceing some issue with an ssl certificate that i need for payment gateway,i already generated it but it doesn't work,i'm already doing a 3d payment gateway with a plugin that requires that certification..
I opened ssl via command prompt generated it but still i get the error request that the certification is invalid,is it possible that i did something wrong here is how it is required
OpenSSL Setup Prior to proceeding, it is necessary to download Win32 OpenSSL which can be found at: https://www.openssl.org/source/ After
the software is set up, it is important to enter a variable Path for a
bin catalogue.
In system variables: Variable PATH → “Change” Put a semicolon at the end of the line and enter a pathway to the bin folder:
c:\OpenSSL\bin For the next step, in the console, open the batch
folder and run run.bat (one of the attachments in the email received
from UPC)
The command can be performed for example in FAR. For this, place the cursor on run.bat file, press Ctrl Enter and add MERCHANT ID with
a space Key Generation Key generation and exchange is performed after
the Merchant sends a request for registration and receives E-shop
attributes via Internet (that includes a Merchant ID) Prior to key
generation, it is necessary to edit the file config.dat according to
the data of the E-shop. Config.dat data shall not strictly correspond
with the data in the request; such data is used for neither signature
generation nor signature verification and is only used for an
identification of a certificate file.
Can someone please explain me a little how to do it in steps i already watched some tutorials on youtube but i think i did something wrong,ill hope someone here can tell me how to fix this issue thank you very much
I have created a new mimik developer account, and I was trying get the edge access token using the command "mimik-edge-cli account get-edge-access-token -t <--id token-->". But I am getting an "Error" as response.
I have tried with my previous account and in that case i am able to get the access token as shown below. Same issue happened for raspberrypi too.
why it is not able to get the access token while using a new account?
Please make sure to copy the ID Token from developer portal correctly, In most cases there might be a hidden character copied. Maybe just try copying the text by highlighting with mouse from first character to the last. Do NOT use the copy to clipboard button. Also please make sure that the edgeEngine on the PI is not associated already by checking with:
mimik-edge-cli account get-me
When you input command above, if you see an ID for value "accountId:" then your PI is already associated an CANNOT be associated again. You have to un-associate first and then associate with the new ID token from new account/project. You can verify that un-association is successful when above command shows empty value for "accountId:"
FOR FUTURE REFERENCE:
Please only tag questions with edgeSDK if it is related to FreeRTOS platform. For all other platforms, please use tag edgeEngine
I already followed the steps exactly specified at this link
However, I am still having the issue. My build will get stuck when accessing the private repo.
$ julia --check-bounds=yes -e 'Pkg.clone("https://github.com/xxxx/xxxx.git")'
INFO: Cloning xxxx from https://github.com/xxxx/xxxx.git
Username for 'https://github.com':
Done: Job Cancelled
Note: I manually cancel it after a few minutes of waiting. How can I get it to use the SSH key I have setup and bypass this username and password field?
Note: xxxx is used in place of the name of my project to make this post general. I have already checked out the links on Travis CI and they don't make it clear what needs to occur. Thank you!
Update: I tried to add a GitHub Token Pkg.clone("https://fake_git_hub_token#github.com/xxxx/xxxx.git") and it still prompts me to sign in with the username. I gave that token full Repo access. Also, note that I am using Travis CL Virtual Machine.
In the Travis CI docs they reference the following:
Assumptions:
The repository you are running the builds for is called “myorg/main” and depends on “myorg/lib1” and “myorg/lib2”.
You know the credentials for a user account that has at least read access to all three repositories.
To pull in dependencies with a password, you will have to use the user name and password in the Git HTTPS URL: https://ci-user:mypassword123#github.com/myorg/lib1.git.
SOLUTION:
just add TravisCIUsername:mypassword#github.com/organizer_of_the_repo/Dependancy.git
In my case, I am going to make a fake admin account to run the tests since someone will have to expose their password to use this setup. Note that you can set up 2-factor authentication on the admin account such that only one person can access it even if they know the password.
You need to add the SSH key to the Travis UI under an environmental variable for your desired repo. You also need to add the key to the .travis.yml file on that repo.
https://docs.travis-ci.com is the docs for Travis
SOLUTION: just add Travis_CI_Username:my_password#github.com/organizer_of_the_repo/Dependancy.git to the travis.yml. file.
If this is unclear, please comment and I will update, but this is how I got it to work for me(even tho I went through all the SSH key business).
In my case, I am going to make a fake admin account to run the tests since someone will have to expose their password to use this setup.
Note that you can set up 2-factor authentication on the admin account such that only one person can access it even if they know the password.
I am creating different workspaces having different types of names containing special characters also sometimes. When I am trying to perform a Full text search nothing comes up in workspace results. Now, problem is how can I start with the debugging process?
What all things to consider during Troubleshooting this issue on both IDOL Indexer and iManage worksite?
Any suggestions? Really Appreciated.
Thanks!
You can enable debugging logs for all interactions through the SDK by turning on middleware Logging - Basically these log the actions performed by iManage.dll.
The log paths registry key will provide the location of the log. Any application using iManage.dll will spawn a new file based on it's process name (such as YOURAPP.txt, WINWORD.txt, OUTLOOK.txt, etc)
Create or set the following values in HKEY_LOCAL_MACHINE\Software\Interwoven\WorkSite\8.0\Common
Name: Middleware Log Path
Type: String
Value: C:\Temp
Name: Middleware Log Flags
Type: DWORD
Value: ffff
This will show you useful information but the best way to debug is to pare your search parameters right back to basics then slowly introduce more complex parameters. Workspace search requests are made up of both IManage.IManProfileSearchParameters and IManage.IManWorkspaceSearchParameters
and I've found that depending on the data sometimes you'll need to search only with the IManProfileSearchParameters and leave IManWorkspaceSearchParameters as default empty parameters.
Inspired by this awesome post on a Git branching model and this one on what a version bumping script actually does, I went about creating my own Git version bumping routine which resulted in a little package called bumpr.
However, I don't like the current way of handling (GitHub) HTTPS credentials. I'm using the solution stated in this post and it works great, but I don't like the fact that I need to store my credentials in plain text in this _netrc file.
So I wondered:
if one could also obfuscate console input when prompting via readline(), scan() or the like in much the same way as when using the Git shell. See code of /R/bump.r at line 454:
input <- readline(paste0("Password for 'https://",
git_user_email, "#github.com': "))
idx <- ifelse(grepl("\\D", input), input, NA)
if (is.na(idx)){
message("Empty password")
message("Exiting")
return(character())
}
git_https_password <- input
how RStudio realizes that a "Insert credentials" box pops up when pushing to a remote Git repository and how they obfuscate the password entry.
if file _netrc is something closely related to the GitHub API or if this works for HTTPS requests in general
Git has a mechanism to store, cache or prompt for credentials. Please read http://git-scm.com/docs/gitcredentials.
Within a script, you can use the git credential command to access it: http://git-scm.com/docs/git-credential