IBM Cloud App ID

I have used the IBM Cloud App ID during my training in IBM Full Stack Course in Coursera. I was able to navigate and explore the tools of IBM Cloud including this IBM Cloud App ID. So far, I was able to successfully use the IBM Cloud App ID as part of my task in the Coursera Training in IBM Cloud, and was able to utilize the service or app.

I was not able to use the IBM Cloud App ID as for the integration of the app into the existing services via code integrations. I was just able to have a chance to use the IBM Cloud App ID during my task in the courses in the Coursera in IBM Full Stack courses.

The service is being used for authentication by the developers for building applications. The users range from students to professors and industry experts to build application projects. App ID manages the authentication process of the application giving more time for the users to spend time on building logic and improving the user experience. It does the job perfectly. It has built-in features that allow authenticated login to the apps using SDKs, APIs, and other user interfaces. It also allows application to application authentication and application to API authentication. Easy to use with loaded features. Documentation provides an easy walkthrough in understanding its application.

The App ID allows excellent authentication of apps. Allows authenticated logins using email and password, social login, and enterprise login.

We use IBM Cloud App ID as authentication system for a demo product, where we want to show how easy it is to integrate with external authentication systems. Cloud App ID acts as a OIDC compliant Security Provider and provides the user Administration for free. So there is no need of programming the user related functionality, like self-registering or forgot password.

We benefitted from this capability by just adding some lines of code and we had the integration to the authentication system. We were also in the position of re-using part of the sample application that was provided. So in general it was very fast and handy.

My company use IBM Cloud App ID for authentication of our clients. Its simplicity is what interests us as we don't want to invest much resources/effort for integration.

This feature helped us avoid a lot of development, testing, and reviewing negative feedback from clients. Just a simple integration and that's it.

We are mainly using IBM Cloud App ID for our client android application in the development department. Since it's client data, we need to make secure access. Now I am managing multi-users [which] are accessing easily. This tool helped us to maintain secure authentication and authorization. Now our users can access applications from any network worry-free.

Yes. Our developers are authenticating easily with tools. They are easily signup and signing easily with an email id and password. No dependency on the IT department to create users for access. Workflow also improved. We can also manage user access easily.

We have used IBM Cloud App ID to add authentication to our EY web app and the mobile version. We have used the social login option. It was used by our practice to tackle a typical business problem of EAD.

Yes, it has really saved a lot of time helping us deliver the app within the crunch deadlines.

IBM Cloud App ID has mainly been used for the website and app, where user login or authentication is required. It also offers advanced capabilities like Single Sign On (SSO) and Multi-factor authentication or 2FA. Also, it is compliant with data regulations like PCI, GDPR, which makes it easy to set up the software without much effort.

IBM Cloud App ID has made it really simple for the developers to add authentication with just a few lines of code, it will also reduce the effort to maintain any infrastructure or compliance because IBM Cloud App ID has already done it. It also makes it easy to have features like Multi-Factor Authentication and Single Sign-On, with the same few lines of code, and the integration is done.

IBM Cloud App ID provides us an easy to use authentication service for applications. It allows our application developers to focus on the development of business logic and user experience with an assurance of authentication being handled by App ID service. The API docs are too good and very helpful for our application developers to integrate their Apps and secure them as needed.

This is very useful as it allows us to easily add standard based authentication with only few lines of code. We can issue API tokens for authentication into your application.

Our company uses IBM Cloud App ID as a simple and authentication login solution for end-users. We use IBM Cloud App ID because it is simple and easy since our use case did not need complex features. IBM Cloud App ID also plays nicely with our app, since our backend runs with the help of IBM Cloud functions. It also helped us to validate the access of end-users to different apps and get access to them.

It's very easy to integrate with the help of step-by-step guide documentation available. Development time was reduced with the help of IBM Cloud App ID. Also, the management of users was made easy. Many testers are repeat testers so having respective credentials for single sign-on reduces the need for multiple registrations. As such, the authentication feature has greatly benefited our use case.

We have few clients with IBM Cloud App Id setup to access IBM Cloud platform. It's used by particular department for enabling federation of associates to access IMB Cloud resources. Thus enterprise users can access without creating manual user login and can use enterprise SSO to sign in. We federate using SAML 2.0 IDP.

It's very easy to integrate with step by step guide documentations available. Definitively helps to get no time to market.

We use App ID as a simple login solution for clients of our SEQu-SUITE line of products so that our clients' admin users will only get to see and edit their company's data.
Instead of creating our own auth server, or using a third-party solution, we used IBM App ID since it is relatively simple considering our use case did not need the additional features of other providers. It also plays nicely with our app, as our backend is run on IBM Cloud Functions, so being able to keep the auth server and app backend on one vendor saves a lot of administrative effort.

I use IBM App ID with IBM Cloud Functions as my backend. It has been easy to integrate App ID with Vue.js. The UI is handled for me. The auth function is handled for me. Turning on auth for Cloud Functions is very easy. I just have to pass the token from App ID to Cloud Functions and CF does the rest.

We are using it as part of apps that we develop for customers. Is used to validate access of end-users to different apps and get access to specific microservices.

This is exactly why we use IBM Cloud App ID. Development time has been reduced thanks to using IBM Cloud App ID. Also the management of users.

IBM Cloud App ID is used to implement SSO between web applications deployed and running in IBM Cloud and IBM Connections running on-premise. App ID addresses the following business problem: it enables a web application to be used only by users authorized by company's LDAP server. Only authorized users can access the web application running in IBM Cloud.

Using IBM Cloud App ID we have easily added authentication to a web application deployed and running in IBM Cloud. The application is now secure and can be accessed only by users authenticated by the company's LDAP.

It is used across the organization for SSO authentication for cloud applications.

IBM App ID is being used by the development team for App to API authentication to solve lack of security at in-between points. Using IBM App ID is helping to create a stronger, secure connection between our API and the app we are developing.

We offer digital transformation solutions to our customers in key geographies and being an IBM business partner, we recommend IBM products to our customers. In fact, we were one of the early adopters of IBM Cloud (then Bluemix). We have used App ID for internal mobile applications. We use Multi-Factor Authentication (MFA) in many of our solutions and with App ID it is easy for us to use MFA. Deployment is quite fast and deployment across channels is easy.

We use it to authenticate our mobile apps. Mostly to get social media login support.