1 Connect Login
Angelika
Virtual urgent care is a video appointment with a board-certified Columbia or Weill Cornell doctor that takes place through your phone, tablet, or computer. A virtual urgent care visit is for non-life-threatening conditions only and is available daily from 8 am until midnight.
Download the NYP Connect App or login in to Connect to make a virtual urgent care appointment. If you need to create an account or have questions, please see Account Creation section or call 646-962-4200.
We are proud to offer video visit technology. A video visit allows you to meet with your provider using your smartphone right from the comfort of your home. Please refer to the instructions below. For any questions or additional support, please call Connect Technical Support at (646) 962-4200.
I was setting up Jamf Connect on a device and was going through the steps but I signed in to the Menu Bar item and think it may have messed things up. When I logged out to get to the login window, I'm getting this error below:
So I was able ot reproduce this. This happens when you do NOT have a login profile installed AND the authbroker is set to Jamf Connect. You can either install a login profile or run the authbroker reset command.
I ran into the same issue and PhillyPhoto's comment: "So I was able to reproduce this. This happens when you do NOT have a login profile installed AND the authbroker is set to Jamf Connect. You can either install a login profile or run the authbroker reset command." prompted me to resolve it.
It might not be relevant to other cases but what I had done prior to this breaking is omit our local service account that's created during enrollment from the scoping of our Jamf Connect Configuration Profiles and Launch Agent Policy. I have also configured our Macs to not allow Guest Accounts or to create Local Accounts outside of the Jamf Connect Login Window. Removing the omission of our Admin Service account from the scope of our Jamf Connect Configurations resolved the issue.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
Signing up for Connect is easy. Ask about joining Connect at your next visit. If you already have an invitation and activation code, visit our sign-up page. If you do not have an activation code, visit our self-sign-up page and follow the directions.
Connect messaging provides an easy and convenient way to communicate with your provider. Through this service, you can send messages to your provider and receive medical advice from the comfort of your home. Learn more about medical advice messaging and billing.
Rest assured, your account remains active and you may continue to access your information. No new health information has been added to your FollowMyHealth account after Feb. 1, 2020, and you can no longer connect to your provider through that account.
To continue to connect with your Columbia providers, sign up for a new Connect account. Your new account will not have all of your health information from your FollowMyHealth account, but after our February launch, your health information will begin to flow to your new Connect account.
We've updated the look and feel of our patient portal. This update is part of our effort to make your Weill Cornell Medicine, NewYork-Presbyterian and Columbia medical records available through Connect in 2020. Your portal may look different, but your access and features remain the same.
Any patient 12 years old or over is eligible for a Connect account. In addition, parents can be given portal proxy access to manage their children's accounts, or patients can grant access to their own accounts to family members, friends, or caregivers. Please see the Terms and Conditions for further information.
We are committed to protecting your privacy and the security of your health information. All communication between you and your healthcare provider and care team using Weill Cornell Connect is carried over a secure, encrypted connection.
You can pay your Weill Cornell Medicine provider bills online through Weill Cornell Connect. Logging into Weill Cornell Connect also allows you to pay bills from Columbia and NewYork-Presbyterian, if you have received services from them.
All electronic fund transfers and payments are compliant with Payment Card Industry (PCI) standards. If you have questions about your statement, please reach out to customer service by calling the phone number on your statement or by sending an electronic message through Connect.
Cannot arrive at the desktop. After entering okta credentials and selecting MFA type (push), once I approve the notification, the Mac goes black full screen momentarily, then returns to the login prompt. Okta mobile app prompts that authentication was successful, however no local account creation or login.
I have Connect Login setup and it is asking for my Azure credentials. I type them in, get the screen asking if I want to stay signed in to reduce logins, Select Yes (or no), the screen goes black for a minute and then goes back to the first screen asking for the username.
Having the same issue on Jamf Connect 2.0. Using the same settings in a new configuration profile as with Jamf Connect 1.xx (where it is still working fine), but it keeps redirecting me back to the login page. I did notice you can login with a local account, while that actually should not work as it is not enabled in the configuration profile, aside from the fact that I'm authenticating to my IdP. Setting your client secret should not be necessary if you've set that option to "Use PKCE" within your IdP, so that shouldn't be the cause..
I am also experiencing this issue. Tried DenyLocal to true also but the issue persists here also. Tried using Use PKCE and setting a client secret and neither seems to change the behavior. Using Okta as the iDP.
I am late to the party. Think the issue is related to having AuthServer & OIDCAuthServer filled out. What I did with the Jamf Connect Config, is just leaving OIDCAuthServer blank and only fill out the Auth Server. If you're using a .plist is just have only AuthServer & get rid of OIDCAuthServer
AuthServer xxx.okta-emea.com BackgroundImage /usr/local/images/xxx.jpg CreateAdminUser DenyLocal EnableFDE HelpURLLogo LocalFallback LoginLogo /usr/local/images/xxx.png LoginScreen OIDCClientID xxxxxxxxxxxx OIDCDefaultLocal OIDCIgnoreAdmin OIDCProvider Okta OIDCRedirectURI xxxxxx
Update - I ran into this issue and worked with Support. Oddly enough, removing any entries not being used in the Config Profile resolved this issue for us with JamfConnect Login and JamfConnect. I would suggest edit the config profile, erase and re-enroll your test device to fully test.
We can't for the life of us figure out why the login loop is happening. We've stripped our plist to barebones (just provider/auth server/access ID) and it's still happening. Funny thing is, if we remove the access ID and instead replace with the Admin ID, it works. So it doesn't like something about the access ID even though that Application is setup identical to the Admin one in Okta (aside from the actual ID of course).
@AdamM01 Removing any entries not being used in the config profile means by de-selecting them / unticking them, so they won't become visible as an empty setting in the plist. Also, is your "Require Network Authentication" key set to True?
I know I'm late to this party. We are authenticating to Azure/O365 and occasionally see this as well. Sometimes it's as simple as switching to different internet like a hotspot and then it connects and authenticates again. I've certainly looked at all of the suggestions here as well. I have been able to log in and create a new account when other existing accounts aren't working. My most recent fix was to delete the user account and leave the home folder in place then sign in with the user's email address let it create the new account and find the old home folder. Fortunately all files and apparently user preferences were there afterward. In my case it appears there was some corruption in the local account. I think the same symptoms we see on the login loop could have multiple causes. Hope this helps someone in the future!
4a15465005