search

certat / do-portal

This project is in maintenance mode and will only receive bug fixes, but no new features. A new version of this software is being developed.
5 stars 5 forks source link

RE: Backend always return 403 #126

Closed vetsolution closed 4 years ago

vetsolution commented 4 years ago

Hello Sorry for opening a new issue but it seem that reply to a closed issue don't send notification. So I repost it here Regards,

Hello, Thank for the info. But in the frontend I cannot add any organisation because I don't have any parent organisation image

Moreover, I cannot specify any ASN, FQDNs,IP Ranges,... as in backend.

I have an another question, where is the EventDb infos I dont see any tabs about it ?

Thank you for your help ;)

Originally posted by @vetsolution in https://github.com/certat/do-portal/issues/125#issuecomment-617667734

MarkHofstetter commented 4 years ago

no problem on opening issues and asking questions, you are very welcome!

  1. create organizations and users:

you have to "bootstrap" the database to make the portal usable

so either create an organisation manually via SQL in the database with your user as the OrgAdmin

or BETTER see python3 demodata.py addyaml demodata.py:def addyaml(): app/fixtures/testfixture.py: def addyaml(yamlfile = "install/testdata.yaml"):

you may either edit the provided yamlfiles (eg master_user.yaml) or create a new one and call the addyaml function

  1. the basic idea for ASN, FQDNs,IP Ranges,... is not to create them manually, we fetch them from the ripe database and import them in a separate schema (fody) in the database
ghost commented 4 years ago

or BETTER see python3 demodata.py addyaml demodata.py:def addyaml(): app/fixtures/testfixture.py: def addyaml(yamlfile = "install/testdata.yaml"):

you may either edit the provided yamlfiles (eg master_user.yaml) or create a new one and call the addyaml function

Can you please add to the installation documentation that the yaml file should be newly created / adapted? Thanks

vetsolution commented 4 years ago

I think the data was already imported. I found the problem, in organisation_membership, the account master@master.master wasn't linked to any organisation.

Another questions: What should I fill in Ripe handle field ? image

Also I dont see any event tabs nor table in db, I though that fody handle event and do-portal include fody, am I wrong ?

Many thanks

ghost commented 4 years ago

Another questions: What should I fill in Ripe handle field ?

The organisation handle (ORG-*-RIPE)

Also I dont see any event tabs nor table in db, I though that fody handle event and do-portal include fody, am I wrong ?

No, fody is not "included" in do-portal. Strictly speaking it is not related, as the RIPE import is not part of fody, but part of the certbund-contact-expert. As we do not re-invent the wheel here, there's no query interface for IntelMQ events table included in do-portal, fody's events/statistics component is doing a good job for that.

vetsolution commented 4 years ago

So I should install fody for event handling, then do-portal for contact management ?

ghost commented 4 years ago

So I should install fody for event handling

What do you mean by event handling?

vetsolution commented 4 years ago

Assign event to a customer (I suppose it's done with DO Portal Expert Bot). Then let customer acces to their event And optional functionality: mark an event as "done"

ghost commented 4 years ago

Assign event to a customer (I suppose it's done with DO Portal Expert Bot). Then let customer acces to their event And optional functionality: mark an event as "done"

That's neither currently possible nor in scope of future developments, sorry.

ghost commented 3 years ago

@vetsolution This software is now in maintenance mode, more information here: https://github.com/certat/do-portal/issues/133