One requirement for my current Meteor project was that a user must login with their ActiveDirectory account. This means that Meteor must be able to authenticate against LDAP. In atmosphere there are already a few packages available which implement and support LDAP authentication. However, they are either outdated or difficult to configure. This is why I’ve decided to build my own custom login request handler for Meteor.
Continue reading “Meteor register LDAP login request handler”
One of the popular features of Meteor is its accounts package. As you know, it makes it fairly easy to add a user authentication solution to your Meteor app or add support for different oAuth services. With the possibility to integrate an Apollo GraphQL API into your Meteor app this became a bit more difficult. The Apollo stack does not support an out of the box solutions to authenticate users with Meteor accounts. Jonas Helfer, one of the Apollo core devs, proposed two ways to authenticate users with your app:
Continue reading “Authenticate Meteor accounts with the Apollo GraphQL API”
As you’ve seen there are 5 models in our application. This is not that much but requires a lot of effort to display them in the client application. As this tutorial doesn’t cover every aspect of a rich 3-tier applicatoin I will show only how you can authenticate the client application and edit the Employer entities.
Continue reading “Build a Java 3-tier application from scratch – Part 5: Client controller”
As part of the user provisioning process in my company every user account gets an Office 365 license.
2 days ago in the after noon I’ve created an new user account, synced it with DirSync and applied an new Office 365 E1 license.
When I’ve tried access the SharePoint Online website via ADFS SSO, I received an error message like this:
Continue reading “New Office 365 user can not be found in directory”
The purpose of this article is to show the intention and implemention of the most common modifications for the ADFS login page.
Out of the box the login form should look like this:
The f.e. is by default the page url, this can confuse the user, due they expect something like “your login” or “Office365 Login”.
Continue reading “ADFS Login Customization”
Today I experienced an exotic behaviour, a client couldn’t access his Office365 page due he wasn’t able to login on the ADFS authentication prompt.
After googling and binging (just kidding, NERD) I found a simple solution.
Continue reading “Office365 ADFS Chrome Login fails”