Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EPP: drop support for ddoc format legaldocs #270

Closed
vohmar opened this issue Nov 28, 2016 · 21 comments
Closed

EPP: drop support for ddoc format legaldocs #270

vohmar opened this issue Nov 28, 2016 · 21 comments
Assignees
Projects
Milestone

Comments

@vohmar
Copy link
Contributor

vohmar commented Nov 28, 2016

legaldocs in ddoc digital signature container format are not accepted by the registry any more. (deprecated and replaced by bdoc container format).

some other updates might be necessary on the registry side as well. ie epp doc

@artur-intech
Copy link
Contributor

I guess docs should be updated as well? At least this one https://github.com/internetee/registry/blob/master/doc/epp/contact.md

@vohmar
Copy link
Contributor Author

vohmar commented Dec 8, 2016

@artur-beljajev Yes you are correct, any reference to ddoc as supported legaldoc file format should be removed. Updated the description.

@artur-intech
Copy link
Contributor

What browsers do we support?

@vohmar
Copy link
Contributor Author

vohmar commented Jan 2, 2017

Good questions - all the latest and greatest: Chrome, Safari, Firefox, MS Edge

@artur-intech
Copy link
Contributor

artur-intech commented Jan 8, 2017

  • https://epp.tld.ee/schema/ee-1.1.xsd should be created
  • epp-xml should have updated version in master to be able to point all gem consumers (registry, epp-client) to the new version

@artur-intech artur-intech self-assigned this Jan 8, 2017
artur-intech pushed a commit that referenced this issue Jan 8, 2017
artur-intech pushed a commit that referenced this issue Jan 8, 2017
@vohmar
Copy link
Contributor Author

vohmar commented Jan 9, 2017

  • https://epp.tld.ee/schema/ee-1.1.xsd - done
  • for new schema file in master I need it in a separate branch that I can merge without affecting the rest of the code until all updates related to this are tested and approved.

artur-intech pushed a commit that referenced this issue Jan 12, 2017
artur-intech pushed a commit that referenced this issue Jan 12, 2017
artur-intech pushed a commit that referenced this issue Jan 12, 2017
artur-intech pushed a commit that referenced this issue Jan 12, 2017
artur-intech pushed a commit that referenced this issue Jan 12, 2017
@artur-intech
Copy link
Contributor

artur-intech commented Jan 12, 2017

№ 2: Agree. It is pointed to branch "epp-xml-6" of epp-xml gem now. Note it must be pointed back to master once tested and before merging.

@artur-intech artur-intech assigned vohmar and unassigned artur-intech Jan 12, 2017
@vohmar
Copy link
Contributor Author

vohmar commented Jan 25, 2017

@artur-beljajev please move schema and schema validation updates to separate branch so we could move only registry level validation updates to production and keep schema updates back until we have more reasons to require updates on registrars' side.

@vohmar vohmar assigned artur-intech and unassigned vohmar Jan 25, 2017
artur-intech pushed a commit that referenced this issue Jan 31, 2017
@artur-intech
Copy link
Contributor

artur-intech commented Jan 31, 2017

artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 2, 2017
artur-intech pushed a commit that referenced this issue Mar 5, 2017
artur-intech pushed a commit that referenced this issue Mar 5, 2017
@artur-intech
Copy link
Contributor

"ddoc" format is now removed from registrar UI (from domains and contacts). It turns out that I actually can only apply this change to front-end, since removing ddoc from backend also affects EPP schema.

Front-end validation is guaranteed to work in the latest versions of Chrome and Firefox.

@artur-intech artur-intech assigned vohmar and unassigned artur-intech Mar 5, 2017
@artur-intech
Copy link
Contributor

See branch "registry-270-no-schema"

@artur-intech artur-intech moved this from In Progress to Testing in Domistry Mar 5, 2017
@vohmar
Copy link
Contributor Author

vohmar commented Mar 6, 2017

merge conflicts on staging:
#408

@vohmar vohmar assigned artur-intech and unassigned vohmar Mar 6, 2017
@artur-intech
Copy link
Contributor

Merged

@artur-intech artur-intech assigned vohmar and unassigned artur-intech Mar 6, 2017
@vohmar
Copy link
Contributor Author

vohmar commented Mar 7, 2017

still the same, can add legaldocs in ddoc format using the portal for registrars (/registrar/domains/edit?domain_name=...) no problem. The branch is merged and deployed - portal version 6a090ab - that is the latest staging version.

@vohmar vohmar assigned artur-intech and unassigned vohmar Mar 7, 2017
@artur-intech artur-intech assigned vohmar and unassigned artur-intech Mar 7, 2017
@vohmar vohmar moved this from Testing to Production in Domistry Mar 7, 2017
@vohmar
Copy link
Contributor Author

vohmar commented Mar 29, 2017

partly solved and in production

@vohmar vohmar closed this as completed Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Domistry
Production
Development

No branches or pull requests

3 participants