-
Notifications
You must be signed in to change notification settings - Fork 5
RE: Backend always return 403 #126
Comments
no problem on opening issues and asking questions, you are very welcome!
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 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 |
I think the data was already imported. Another questions: 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 |
The organisation handle (
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. |
So I should install fody for event handling, then do-portal for contact management ? |
What do you mean by event handling? |
Assign event to a customer (I suppose it's done with DO Portal Expert Bot). |
That's neither currently possible nor in scope of future developments, sorry. |
@vetsolution This software is now in maintenance mode, more information here: #133 |
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
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 #125 (comment)
The text was updated successfully, but these errors were encountered: