gigya / schema-editor

Used to manage a Gigya Registration-as-a-Service database schema

schema-editor

Used to manage a Gigya Registration-as-a-Service database schema. More information about the database schemas can be found here: http://developers.gigya.com/display/GD/Identity+Storage http://developers.gigya.com/display/GD/Data+Store

This tool is currently hosted at: https://tools.gigya-cs.com/schema/

The tool allows you to manage Registration-as-a-Service (Identity Storage) and Data Store database schemas. It uses the following publicly documented Gigya APIs: http://developers.gigya.com/display/GD/accounts.getSchema+REST http://developers.gigya.com/display/GD/accounts.setSchema+REST http://developers.gigya.com/display/GD/ds.getSchema+REST http://developers.gigya.com/display/GD/ds.setSchema+REST

The tool requires you to have access to a Gigya API key and the associated partner secret in order to make changes to a schema.

For other relevant tools, please see the Gigya-RaaS-Toolkit located here: https://github.com/scotthovestadt/gigya-raas-toolkit

schema-editor's Issues

[rl-reuse_tool-1] Violation against OSS Rules of Play

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-1
Explanation: Does README mention REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

Allow filtering by a csv list of fields

Allow a csv list of fields to be displayed after getSchema to make it easier to filter the schema for making changes.

This is particularly useful for large schemas where you will not be able to save the whole form directly without deleting a number of fields.

setSchema should be a POST

If the schema is large, a GET request will exceed the 2,000 character limit. We should POST the data for setSchema requests.

[rl-reuse_tool-2] Violation against OSS Rules of Play

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-2
Explanation: Does it have LICENSES directory with licenses? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

Large schemas fail to save

Consider splitting the schema into chunks and posting to the server slowly.

Field values are not escaped (quotes leak HTML)

Only showing fields with writeAccess: clientModify

Fields set to writeAccess: serverOnly are not appearing in the Schema Editor, even though the fields are returned in an accounts.getSchema call through the Gigya API Tool.

[rl-reuse_tool-4] Violation against OSS Rules of Play

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-4
Explanation: Is it compliant with REUSE rules? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

[rl-assigned_teams-1] Violation against OSS Rules of Play

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-assigned_teams-1
Explanation: Does it have enough teams on GitHub? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

Unset field type on profile schema

Since we cannot edit the field type of profile schema fields, we should NOT include this when SAVING the schema so we do not get errors.

[rl-license_file-1] Violation against OSS Rules of Play

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-license_file-1
Explanation: Does it have a license file? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

[rl-reuse_tool-3] Violation against OSS Rules of Play

A violation against the OSS Rules of Play has been detected.

Rule ID: rl-reuse_tool-3
Explanation: Is it registered in REUSE? No

Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html

Formats containing regex() break the form

When a format contains a regex() description, the quotes are not properly escaped, breaking the form:

<input 
    type="text"
    id="profileSchemaInput[173][format]"
    data-property="format"
    data-schemarow="profile[173]"
    value="regex(" ^[_a-za-z0-9-]+(\.[_a-za-z0-9-]+)*@[a-za-z0-9-]+(\.[a-za-z0-9-]+)*(\.[a-za-z]{2,4})$')'=""
>

I am not 100% positive what the correct solution is here (html-encoding or escaping).

Generate schema automatically from screensets.