Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0.M3
    • Component/s: GWT
    • Labels:
      None

      Description

      By the time we ship M2, we should be able to articulate our security plans.

      • Will we rely entirely upon Spring Security? If not, what will we do in its absence?
      • How much of its feature set will we expose client side?

      My suspicion is that we won't be able to provide all the bells and whistles, e.g. hiding or disabling pieces of the UI that the user is not authorized for.

        Activity

        Hide
        Unnur Gretarsdottir added a comment -

        This is done, We are providing a UserInformation class which does no authentication by default (this implementation is baked into GWT). This class can be overriden, and in the generated app, we will generate GaeUserInformation, which uses AppEngine authentication.

        Show
        Unnur Gretarsdottir added a comment - This is done, We are providing a UserInformation class which does no authentication by default (this implementation is baked into GWT). This class can be overriden, and in the generated app, we will generate GaeUserInformation, which uses AppEngine authentication.

          People

          • Assignee:
            Unnur Gretarsdottir
            Reporter:
            Ray Ryan
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: