Skip to main content
kahsbnxasxwasx
kahsbnxasxwasx
Known Participant
October 31, 2011
Answered

Hello, may I ask how to prevent the illegal distribution of video and POST data

  • October 31, 2011
  • 1 reply
  • 1356 views

setPublishPassword  and setPostingPassword Helpful?I do not quite understand, do not use an example. Ideas or examples can you provide a

But those methods are the client, I set him groupspecWithOutAuthorizations, but was illegally set to groupspecWithAuthorizations how to do ah。

    This topic has been closed for replies.
    Correct answer Michael Thornburgh

    the groupspecWithAuthorizations includes the passwords. therefore, the groupspecWithAuthorizations must be treated as a secret password. it must only be given to clients that are allowed to publish/post in your group.

    one way to do this is to generate the groupspec strings in a central place (either on an authorized client, or on FMS), and only give out the pre-computed groupspec strings to other clients. since all of the information (including passwords) is needed to generate the groupspec using the GroupSpecifier class, you don't want to generate the groupspecs using GroupSpecifier on each client, since that would involve transmitting the passwords to every client, whether each was authorized for publish/post or not.

    1 reply

    kahsbnxasxwasx
    kahsbnxasxwasxAuthor
    Known Participant
    October 31, 2011

    Someone help you, I point wrong, I did not solve the problem, has been plagued for several days. I set the password, but that these passwords are written on the client, it is not being seen, ah

    kahsbnxasxwasx
    kahsbnxasxwasxAuthor
    Known Participant
    November 1, 2011

    Hello, master. My question is, I gave tourists groupSpecWithoutAuthorizations (), but he can easily access after login to groupSpecWithAuthorizations () value, then you can as a tourist, but there are POST and publish permissions, and ask how to deal with this

    M
    Adobe Employee
    Michael ThornburghCorrect answer
    Adobe Employee
    November 3, 2011

    the groupspecWithAuthorizations includes the passwords. therefore, the groupspecWithAuthorizations must be treated as a secret password. it must only be given to clients that are allowed to publish/post in your group.

    one way to do this is to generate the groupspec strings in a central place (either on an authorized client, or on FMS), and only give out the pre-computed groupspec strings to other clients. since all of the information (including passwords) is needed to generate the groupspec using the GroupSpecifier class, you don't want to generate the groupspecs using GroupSpecifier on each client, since that would involve transmitting the passwords to every client, whether each was authorized for publish/post or not.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices