Uploaded image for project: 'Identity Provider'
  1. Identity Provider
  2. IDP-1489

Promote CAS profile config into API

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0
    • Component/s: CAS, Configuration
    • Labels:
      None

      Description

      I'll listen to objections, but the approach we took with SAML was to put the ProfileConfiguration classes into the API because they're very "exposed" to the deployer to know what settings exist.

      We have other cases where we have to direct people into javadocs for impl classes but we try and minimize them. The V4 change would be an opportunity to line that up and move them, and I'm inclined to, but as I say, I'll listen to concerns before I do it.

        Attachments

          Activity

            People

            Assignee:
            cantor.2@osu.edu Scott Cantor
            Reporter:
            cantor.2@osu.edu Scott Cantor
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 45 minutes
                45m