Scribd
Upload
441 views

Basic of OB Configs

The document provides instructions for using the OB tool to create an automation configuration for logging into the 9anime website. It describes downloading and opening OB, creating a new configuration, and using various block types like requests, key checks, and parses. It then walks through capturing a login request, parsing out variables like the username, password, and token, and using those to build a request block to log a user into the site and check if the login was successful.

Uploaded by

akshat yadav
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
441 views

Basic of OB Configs

The document provides instructions for using the OB tool to create an automation configuration for logging into the 9anime website. It describes downloading and opening OB, creating a new configuration, and using various block types like requests, key checks, and parses. It then walks through capturing a login request, parsing out variables like the username, password, and token, and using those to build a request block to log a user into the site and check if the login was successful.

Uploaded by

akshat yadav
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

FIrstly you will need to download OB from the link above and once you open it a few

files will be generated. After it is open you will go to the configs section you
will be using the stacker (editor) to start you will just create a config. Click
the new button. I have named it 9anime.

Click accept to be taking to the stacker now you are in config editing mode.
Key Terms:

Icon 1 - Add a block


Icon 2 - Delete a block
Icon 3 - Disable a block (good for testing)
Icon 4 - Duplicate a block
Icon 5 - Move a selected block up
Icon 6 - Move a selected block down
Icon 7 - Save (Remember to do often)

The first section of blocks are request based and the bottom half are selenium
based (browser automation)
Request - Can be post or get and used for logging in and grabbing content on the
web page. When you are posting or getting with a request a response (text) will
usually be given
Key Check - Used to sort if an account is a fail or a success. For example if a
response is "fail" after posting you would use a key check to tag the account under
a fail but it the response was "success" you would get the key check to add the to
success.
Parse - Used for capturing specific parts of a response and browsers cookies

To start we are going to need to capture some requests and you can do this in
google chrome! Press CTRL - SHIFT - I. Which will open up inspect you will want to
select the network section to view requests. Once we are on the anonfile login page
we will need to enter some test data like I have. Does not need to be real.

Now that we know how anonfile posts login request we can create a request block by
using the add button on the config stacker.
Fill in all of this in OB it should be under this is network inspect (make sure you
are viewing the right request)

URL = Request URL


Content-Type = Request headers/content-type
Request Type = Request Method
Now for the important part is getting the post data correct you will need to scroll
down to view the full request and find the "/form data" section

You can't directly request that you will need to click on "view source"

The first part of the post data is simple a user name is always represented
"<USER>" (no quotations) and "<PASS>"
If your data was zach@pruned_36514175.nonova:sad
<USER> = [email protected]
<PASS> = sad
Now that we know that post data will be

username=<USER>&password=<PASS>&_token=syHwak3IW0wAvEUOObDHqDygBjyAwGDpXCRfZjIn
Since we don't know the token yet now it is time to find it. Sometimes it can be
under a cookie or a browser response. In this case its a hidden response by getting
the site URL (not posting)

As demonstrated I have searched for a token (response is always showed in green


make sure log is selected. Data will be used later) This is usually the way you go
when looking for a token. Now we need to capture the token so we can reference it
like with <USER> and <PASS>

Key Terms:
Var/Cap Name: What will be called so <TOKEN>
Parse: <SOURCE> is default and all we need
Left/Right string: For example if you are wanting to only capture "configs" out of
"I like (configs)". Left string would be "I like (". Right String would be ")"

To test what we have done we will click the start button!

Now if the token that we captured looks like the one earlier in the captured post
request. That's great. Time to make the login request!

Since we captured the token the post data would now be:
username=<USER>&password=<PASS>&_token=<TOKEN>
Your post request block should look like this:

Since we are posting directly to the site if there is a fail the site shows
"Invalid username or password." We can use the with a keycheck to know if an
account is working or not.

This is a very simple key check has one sub block of type fail. If it contains
"Invalid username or password.". and a success block if the source does not contain
"Invalid username or password.". To make sure you got this right you can make a
sample account and enter that in to data and see if you get a success response (if
its a valid account and you don't get a success you have made a mistake) Then you
also test fake accounts to make sure its giving a fail.

You might also like