Download the PHP package socialiteproviders/imis without Composer
On this page you can find all versions of the php package socialiteproviders/imis. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package imis
IMIS
Installation & Basic Usage
Please see the Base Installation Guide, then follow the provider specific instructions below.
Add configuration to config/services.php
Add provider event listener
Laravel 11+
In Laravel 11, the default EventServiceProvider provider was removed. Instead, add the listener using the listen method on the Event facade, in your AppServiceProvider boot method.
- Note: You do not need to add anything for the built-in socialite providers unless you override them with your own providers.
Laravel 10 or below
Configure the package's listener to listen for `SocialiteWasCalled` events. Add the event to your `listen[]` array in `app/Providers/EventServiceProvider`. See the [Base Installation Guide](https://socialiteproviders.com/usage/) for detailed instructions.Usage
You should now be able to use the provider like you would regularly use Socialite (assuming you have the facade installed):
Example env
Creating the IMIS UserInfo Query
Create directory in root: 'OAuth2' and create query inside this directory.
Define > Summary Tab
-
Name: userInfo
-
Description:
SSO user Info Built to OAuth2 Standards https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims
Define > Sources Tab
- Sources: UserData + PartyData
- Relations: Custom (When UserData.Party Id = PartyData.Party Id)
Define > Filters
- Property: Where PartyData.Party Id
- Function: None
- Comparison: Equal
- Value: Dynamic
- LoggedInUserKey
- Prompt: No
- Limit number of results to 1
Define > Display
- PartyData.Party Id - Alias 'sub'
- UserData.Username - Alias 'username'
- UserData.Email - Alias 'email'
- PartyData.First Name - Alias 'given_name'
- PartyData.Last Name - Alias 'family_name'
Response
Helpful tips
- SSO Setup Info
- Migrating from IQA to Query Service
- In IMIS use the same name for the Client ID and the SSO content item
- A custom query needs to be created to return the user info, userInfo endpoints are not supported by Imis
- Imis returns a 'refresh_token' instead of the auth code so the provider has been modified to handle this.
- Imis does return values when a user is not logged in. The refresh_token and bearer token relate to a Guest user. As the guest user has no user attributes, we should not allow this in our laravel app. This is how I handle this:
Returned User fields
idnicknamenameemailavataruser[]
