Hi All,
With recent updates to Entra ID as well as the rebranding by Microsoft looking into a refresh of the component. It looks like many organisations will continue to be on OS11 for a number of years so expect this component will continue to be important to the community for a while to come. With that in mind wanted to ask if there were any features or suggested updates that people would like to see. Hopefully won't be too inundated with too many suggestions or conflicting ideas that it becomes unwieldy. As always, this is supported on a voluntary basis so any delivery timelines, design decisions and documentation updates will be dependent on availability.
Suggestions in the comments, please.
Hi Paul,Your post comes at the perfect time. I recently had to troubleshoot an issue on a customer and I have some suggestions to make.(A) Does it make sense to add an index in the TokenRequest entity / column StateGuid?MicrosoftLoginConnectorCore > OAuth2_GetAndParseTokenMicrosoftLoginConnectorCore > OAuth2_GetAndParseToken_v2These actions have aggregates querying the TokenRequest entity by StateGuid.(B) In the MicrosoftLoginConnectorCore module there is a CleanTokenRequest timer.The timer has an advanced SQL with this statement:
DELETE FROM {TokenRequest}WHERE {TokenRequest}.[UpdatedOn] <= @DateAND ({TokenRequest}.[Email] = @Empty or{TokenRequest}.[Access_token] = @Empty )Would it make more sense to clean expired tokens?So maybe look at the {TokenRequest}.[ExpiresOn] attribute in the SQL?
Cheers,João Heleno
Joao - Thanks for you suggestions and insight
Hi Paul, I've been trying to use the component to connect to a personal OneDrive folder. This has been a rather challenging experience.
While researching this, I found that the component seems to be still using the legacy Azure Active Directory Authentication Library (ADAL) v1 endpoints instead of the newer Microsoft Authentication Library (MSAL) v2 endpoints.
Also have a look at the link below why it should be advisable to migrate to v2https://learn.microsoft.com/en-us/entra/identity-platform/msal-migration
Since all Microsoft support and development for ADAL, including security fixes, ended on June 30, 2023. this would be a nice time to migrate the component to v2.
Maybe a new major version would be a nice approach, since this might create breaking changes.Kind regards,Kilian Croese
Hi Kilian,
Thanks for you feedback. Will add your notes to the backlog.