Is there any way I can authenticate on GitHub from my Windows 10 VM so that I can push the changes?
Right now the Edge is just sits there with the disabled button "Authenticate".
I know in Linux I can set the user id in some configuration file, but it looks like its not happening on Windows.
Is there any other way?
You should see a Sign In button when visiting https://github.com/login: that would allow you to authenticate on the remote side.
From your VM, using the latest Git for Windows, you will also authenticate when pushing for the first time to a GitHub repository: the credential helper will use the Windows credential manager to cache your GitHub credentials.
Related
My company implemented a plugin for GitHub that scans repository code and warns about security violations.
I need to implement UI automation tests for this plugin so I manually created a dedicated user in GitHub and also created a repository with some files.
In my tests, I need to log in to GitHub via UI, which means navigating to https: https://github.com/, entering username and password, and clicking on the sign-in button.
Things work fine on my local machine but when trying to run it from Jenkins machine Github sends a device verification code to my Gmail account that is connected to the GitHub user and the test failed.
This happens although I disabled the Two-factor authentication mechanism in my GitHub account.
I’m wondering what is the best way to solve this issue.
I am able to login GitHub account on Web login. But in Windows desktop app,
I am able to publish, fork and clone repository but at the time of initial commit, it is always saying authentication issue.
I have tried all the points given in popup-box as by signing-out and signing-in again, by creating GitHub PAT (Personal access token) token also.
I have checked my account settings, In settings, the main branch is the default branch and SSH is also enabled in app and the repository type is public. Even I am able to see changes and created repositories on web login also.
Usually it'll be a credential problem, but it is not. What should I do?
I want to prompt website user to open already installed thin client when they click on a button with their consent through browser prompt.
Following is an example, wherein, after user is authenticated github asks to launch locally installed github client.
Register a URL protocol for your native app. Then in your web app, redirect to a URL that starts with that protocol.
Let's say you've set up a protocol myuniqueappname for the native app, prepare a URL that it can understand:
myuniqueappname://view/123
then use a link to help user navigate to it:
View it on the desktop app
The browser will prompt you to open the link in the native app:
References
Windows: https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa767914(v=vs.85)?redirectedfrom=MSDN
Registering an Application to a URI Scheme in windows 10
Mac: https://developer.apple.com/documentation/xcode/defining-a-custom-url-scheme-for-your-app
https://superuser.com/questions/548119/how-do-i-configure-custom-url-handlers-on-os-x
I am working with ofmeet plugin in openfire for one to one video call functionality and i am following this link for video call like serverIp:portnumber/ofmeet/groupname -> http://serverip:7070/ofmeet/new1 working perfectly and i have follow this link using my mobile app display popup when i add a openfire registered username and password, it becomes a login but i need to token based authentication like not needed popup for userauthentication.
please suggest me and give me step for any tokenbased authentication plugin in openfire + ofmeet plugin.
Openfire-version:- 4.3.2
Openfire Meetings:- 0.9.5
Solved issue using either of two things
1) Enable anonymous authentication on your openfire server.
2) Write your own wrapper like I did in Pade and set username/password. See https://github.com/igniterealtime/Pade/blob/4259462f1d2129a4347eadbc1a57de4eaaab3e64/extension/jitsi-meet/chrome.ofmeet.js#L1028 2
We have a Add hoc distribution for enterprice apps by a secure website. Since version 5 we have a problem with authentication in combination with IIS7. The user logs in with a windows username and password and clicks download. Then a "itms-services://?action=download-manifest&url=domain" action is been started.
Before IOS 5:
The user goes to url, types the username and password. The user press download and again the user need to type the username and password. The application is been installed.
After installing IOS 5:
The user goes to url, types the username and password. The user press download and get a domain "...." not found. There is no popup again, with the credentials, like before version of IOS 5..
This solution was working for a half year, but since IOS5 it doesnt work anymore...
IIS Log
When going to the website and clicking on the action=download that contains the Plist file the IIS shows 401 errors (not authenticated). But when I access the .plist or ipa file directly by url in safari I do get a POPUP to authenticate.
It look like there is a bug in IOS 5 "itms-services://?action=download-manifest&url=domain" actions does not support to authenticate....
Check your plist file if it points to an existing ipa file. If you're using .htaccess to authenticate with a ldap directory you'll need to authenticate once for the plist access and once for the ipa access.
This sounds like a variation of the double-hop problem in which the originally supplied credentials are not being appropriately passed to the second step in your download routine (or web service call, etc.). http://blogs.msdn.com/b/knowledgecast/archive/2007/01/31/the-double-hop-problem.aspx
The fact that you previously had to enter the user name and password twice would seem to support this suggestion. The error that you're receiving that domain '...' does not exist could indicate that the credential being passed to step two is a local machine account that IIS is running under.
If you can get some logging on this process I would want to determine what the authentication/credentials are that get passed at each step. It's possible that something in IOS 5 changed the way that impersonation is handled but I think that's likely just a symptom of how either IIS is set up or the final request is being passed.