Open
Conversation
Contributor
|
I think it would be cool to specify the default project in the config - or at least the project should always be the same, not random at login. Is that possible? |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request provides the backend logic to reduce the selection of projects a user can login to. This is done by identifying projects with identical 'login background'.
For example, several projects my be loaded from the same ALM server. Logging in to one project will always lead to be logged in to all projects (multi-project login realized via connectors). Instead of focussing on projects to login, we introduce the concept of LoginPoints to login in to.
LoginPoints are generated by asking every existing connector for an unique LoginPoint string (e.g., <ALM-Type>-<ALM-Server URL>). Connectors can decide themselves what information to embedd to the LoginPoint string in order to be comparable. In case multiple connectors generate the same LoginPoint string, they can be considered as one LoginPoint group. For each LoginPoint group, it is enough to login to just one project of that group in order to be logged in to each project.
We introduced a new REST endpoint called
loginpoints.This will return pairs of
Example: http://<specmate-server>/services/rest/loginpoints